[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Option to trim packages
- Subject: Re: Option to trim packages
- From: Thomas Klausner <wiz%NetBSD.org@localhost>
- Date: Fri, 24 Apr 2009 11:57:27 +0200
On Fri, Apr 24, 2009 at 12:44:50PM +0300, Hasso Tepper wrote:
> Stephen Borrill wrote:
> > So something like PKG_MULTIPLE_PLIST=libs devel demos and then
> > PLIST.libs PLIST.devel and PLIST.demos
> > It would easy to have a mk.conf option which combined the PLISTs and
> > made one monolithic package (as now) - probably even on by default for
> > compatibility.
> I'd love to see that, but I think it should be much more than simple PLIST
> hack. For example different binary packages built from one source might
> have different runtime dependencies. Imagine audio frameworks like
> gstreamer and akode - every plugin has it's own dependencies.
Additionally, the dependency tracking is much more difficult --
e.g. what does it mean that "kdelibs3" depends on jpeg? Which parts of
the package depend on which part of the jpeg package?
This is not a simple problem, and it will take much effort.
Main Index |
Thread Index |