Date: Fri, 03 Nov 2006 11:28:26 -0200 From: Jean Milanez Melo <jmelo@freebsdbrasil.com.br> To: Jeremie Le Hen <jeremie@le-hen.org> Cc: small@freebsd.org, current@freebsd.org Subject: Re: [fbsd] [HEADSUP] TinyBSD and ports applications Message-ID: <454B43FA.9090303@freebsdbrasil.com.br> In-Reply-To: <20061102164938.GU20405@obiwan.tataz.chchile.org> References: <45489618.2000106@freebsdbrasil.com.br> <20061102164938.GU20405@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremie Le Hen wrote: > I read the description thoroughly. This is interesting and neat, > but I am anxious about stale dependencies left by > "temporary-installed" ports. > > For instance, lets's you're building a TinyBSD image with > net/nemesis which depends on net/libnet10. You neither have this > later port installed. The current TinyBSD implementation will > leave net/libnet10 installed on the build system, although I agree > this is more a problem relatde to port infrastructure which doesn't > record whether a port is an implied dependency or has been > explicitely installed by the user. AFAIK. > > A workaround could be to null-mount the ports directory into the > temporary folder were the TinyBSD image is built, then chroot into > this folder and install the port from here. Afterward you would > remove www,doc,share,include,man stuff. > > I'm not sure if the gain is worth coding. This is maybe going to > be fixed in the ports infrastructure. > Yes, that is the question related to ports, i'll follow your advice, i'll make some tests in a nullfs and if everything works fine we can change the install_ports function. Jean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?454B43FA.9090303>