packg mngmnt model & other cygwin package releases...(where did they come from?)

Brian Dessent
Thu Feb 24 15:51:00 GMT 2005

Linda W wrote:

>         Ahhh...hmm...I haven't understood (and am not entirely sure, if
> yet, I do) the package release mechanism.  I would have thought that
> package maintainers would have been able to check in their packages
> directly -- perhaps, at least, under the experimental release section.
>         If I understand you correctly, package maintainers first have
> to announce something on cygwin-apps, then a few people who have
> "cygwin-package approval" status eventually find the time to check in the
> change?

No, you misunderstand.  Once the package has been approved the first
time, a maintainer can post a new version at any time in the future just
by saying "please upload new version x.y-z" and it is usually done by
someone with a sourceware account within a few hours.  There is no
approval or review involved.  Maybe you should actually review how this
all works before making long rants about it?

There is not the level of handholding that you invision.  In fact it's
even less now, as the new package policy is that any package that's
included in standard linux distros (I think debian is the one used as a
test) gets automatic approval.  All a new package requires is a GTG
review to make sure it's packaged competently.  Before, it required
votes from other package maintainers in addition to a review.

Your rant about "stuff not in cygwin" should be directed to the people
that decided not to contribute them.  In a lot of cases, someone wants
to "support" a package by making a single version of it available and
then never be seen again.  The cygwin project does not have many demands
of a "package maintainer" but the few demands that it does make require
that the person read cygwin-apps and generally be available when
problems arise.  For some people, that's too much, so they just post
junk on some site somewhere and ignore it until the heat death of the

In the specific case of cdrecord, check the archives.  It's been
discussed plenty.  There was a licensing issue.


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list