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. JeanReceived on Fri Nov 03 2006 - 13:29:26 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:02 UTC