This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Maintainers/Packages List, 2003-11-22

On 2003-11-22T19:31-0500, Sergey Okhapkin wrote:
) > ) >initscripts             Sergey Okhapkin         !!! no
) > source and no external-source !!! last updated 2002-11-19
) > ) Shouldn't need source since it is source.
) > Alrighty; another binary-only.
) Do you mean "source-only"?-)

There are only three "source-only" packages: gcc-core, which is just the
-src for the gcc package; gcc-testsuite, which is just the
gcc-3.3.1-3/gcc/testsuite/ directory pulled from gcc-core; and setup.

In setup-ese, initscripts-0.9-1.tar.bz2 is "binary" (or "install").
initscripts-0.9-1-src.tar.bz2 would be its "source". The binary-only flag is
just internal for now, but if we do make it directly tunable by you guys I
can call it "install-only" if that would be more clear. Either way it would
be fully explained.

There are a bunch of packages that do *not* have sources, but *do* appear to
be built from some kind of "source", and that's what that particular warning
was all about. For example (not to pick on anyone), emacs-X11 includes an
.exe in its "install", but there is no -src, and its setup.hint does not
include an external-source. I am not sure it is a major problem now, but the
precedent seems to be to have a reference to the sources, and it is
conceivable some future enhancement may depend on having a complete mapping
of install->source packages. In any event, it doesn't really cost anything
to make sure the external-source is in place.

Daniel Reed <>
It is a miracle that curiosity survives formal education. -- Albert
Einstein, Physicist

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]