On 8/29/07, Alan Coopersmith <[EMAIL PROTECTED]> wrote: > Martin Man wrote: > > For interested parties, I work for Sun as a sustaining engineer and I do > > have a regular problem to "apt-get source -b" some of our software > > packages. I'm not proud of that and I was hoping Indiana will finally > > bring order to chaos... > > But many of the gates aren't designed to allow you to build just the > sources to one package - the source <-> package naming is very strange > in many of them, especially those like ON and X that had the package > breakdown done years ago. > > Do you really want to do "apt-get source SUNWcsr" and have it get the > entire ON source tree?
Just because the packaging and install system supports source installs, doesn't mean that every project will initially provide source. Also a personal long term goal of mine is to eventual sort out the nest of cyclical dependencies in ON and streamline that consolidation. (There is a hell of a lot that I need to learn between now and that time, so that I can even determine if it is possible). > JDS designed their package breakdown to match the RPM model, with > the binary packages closely matching the source packages, but even > SFW isn't a good fit for that model today, with a single man page > package covering all the components. > > -- > -Alan Coopersmith- [EMAIL PROTECTED] > Sun Microsystems, Inc. - X Window System Engineering > > _______________________________________________ > indiana-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/indiana-discuss > -- - Brian Gupta http://opensolaris.org/os/project/nycosug/ _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
