Date: Thu, 16 Feb 2017 16:21:03 -0500 From: Daryl Richards <daryl@isletech.net> To: freebsd-ports@freebsd.org Subject: Re: The future of portmaster Message-ID: <a0a4a666-4787-5e1d-78dc-51e0bcbd0df0@isletech.net> In-Reply-To: <7d0525ee-980e-a63a-f90f-974a7e1022cf@columbus.rr.com> References: <CAB88xy_RU5TTE=pcsjCWsxWyU-jP91qzD9S-R1v6GKGHJg2=nQ@mail.gmail.com> <945f6d92-6834-7e2c-18c4-0a17e2c04122@columbus.rr.com> <44shneot7h.fsf@lowell-desk.lan> <079d97d0-8dc7-8dcd-460e-86644f12b900@columbus.rr.com> <1244d826-e4ae-97a9-6033-8a1c79c2da9e@m5p.com> <7d0525ee-980e-a63a-f90f-974a7e1022cf@columbus.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> While I understand the interest in chroot/jails as an optional >> feature, I hope it doesn't become required. The current non-use >> of chroot/jails is, for me, a feature -- not a bug. -- George >> >> > > Having built and packaged linux from scratch using the rpm package > manager, I came to find that if one is building packages to be used on > multiple machines, one needs to build each package in a chroot > environment or the package could inherit things from the parent not > found in the target machine. Here by making the package unusable. For those of use who have a half-dozen machines, all with differing options, having a central build machine doesn't make a lot of sense. Have a tool like portmaster, for ease of local building and upgrading of ports, is very useful. Just my 2c worth. I'm glad to see people believing there is still a place for a tool like this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a0a4a666-4787-5e1d-78dc-51e0bcbd0df0>