At Sat, 01 Dec 2012 09:22:52 -0300, Nicolás Reynolds wrote: > "Luke T. Shumaker" <[email protected]> writes: > > At Fri, 30 Nov 2012 15:29:56 -0300, > > Nicolás Reynolds wrote: > >> but srcdest is for downloading sources... why copying if you can have > >> them all in the same place anyway? :D > > > > Because the file ownership of the outside srcdest (you) and the inside > > srcdest ("nobody") are different. > > changing ownership is cheaper than copying files i think and you don't > have to trap it to keep them in sync
OK. https://labs.parabola.nu/issues/251 > >> that's the problem with making it mount everytime instead of using > >> fstab, you can end up with the same dir bind mounted many many times. > > > > I think I fixed that bug. Before it trapped the signals so that when > > there was an error, it went to the umount function. The first thing > > that function did was reset the traps to the exit function. This was > > bad because it meant that it might exit early and not umount > > everything. > > > > I think that modifying the outside fstab is too invasive into the > > user's system. > > we could also check if it's already mounted, just in case Good idea. https://labs.parabola.nu/issues/262 > >> > * the legacy code that only runs if systemd-nspawn isn't available > >> > >> this should be deprecated imo > > > > I agree, but removing it would involve patching devtools even more > > than I already do. I'm trying to keep it so that I can still pull > > changes from devtools. > > ok... have you asked about the gplv2? The chroot/systemd-nspawn code is in chroottools.git, which is a fork of devtools.git. The GPLv2/3+ issue is that some of the code hopped from devtools.git to libretools.git. I've been thinking about it; all of the code that hopped is from makechrootpkg, so I think it might be a good idea to rework makechrootpkg into "chroot-functions" or something to keep them separated for licensing reasons, and so that I can pull devtools changes to that code. https://labs.parabola.nu/issues/263 > >> > And some of the "checks" can only be done with a chroot, such as > >> > turning networking off during the build and package stages. > >> > >> this is true, but what we're discussing (except from the "running any > >> command instead of a predefined set" part) does still apply. > > > > I'm not sure what you mean. In order to toggle the networking you must > > exit and re-enter the chroot. > > i mean the changes we're discussing aren't specific to the way the > chroot is handled and benefit both :O OK, I'm going to give libremakepkg a flag to not use the chroot. It should be fairly stright-forward. https://labs.parabola.nu/issues/264 > feature request: is it possible to run dbus+avahi-daemon on the chroot, > or make it available from the host system? now that avahi is a > dependency of distcc i wanted to try +zeroconf (my build machines are > changing ips a lot lately...) but it couldn't connect to the host avahi. I'll look into doing that. https://labs.parabola.nu/issues/265 Happy hacking, ~ Luke Shumaker _______________________________________________ Dev mailing list [email protected] https://lists.parabolagnulinux.org/mailman/listinfo/dev
