On Tue, Jul 23, 2013 at 02:54:29PM -0500, Yaakov (Cygwin/X) wrote: >On 2013-07-23 11:16, Christopher Faylor wrote: >> On Tue, Jul 23, 2013 at 03:20:11AM -0500, Yaakov (Cygwin/X) wrote: >>> This is one case where IMO genini is better than upset: genini-generated >>> setup.ini's don't list source-only packages in setup's package selector, >>> while still being available through the "Src" option of any of its >>> subpackages. Could upset be changed to match, which would avoid this >>> problem for *all* source-only packages? >> >> Why not just rename the package "gcc-src" to make it clear what's going >> on? > >gcc is only one example; many packages (most being library-only) have a >source-only "main" package. Not listing them while still allowing Src >(as genini does) makes things very clear IMHO.
Yes, I got that you like the probable bug that caused genini to not list these packages. The fact that there are multiple packages with this issue isn't really an advertisement for clarity. "I'm looking for the source for gcc but the only thing I could find was the source for gcc-java" isn't really very clear. Nor is the sdesc for gcc which says "GNU Compiler Collection". That's just misleading. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple