Date: Thu, 16 Feb 2017 13:22:03 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: <freebsd-ports@freebsd.org> Subject: Re: The future of portmaster Message-ID: <9ffa861978cdb1a06a69d7b9af525ad5@ultimatedns.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
On Thu, 16 Feb 2017 15:48:57 -0500 Baho Utot <baho-utot@columbus.rr.com> wrote > On 02/16/17 15:40, George Mitchell wrote: > > On 02/16/17 15:33, Baho Utot wrote: > >> > >> > >> On 02/16/17 14:01, Lowell Gilbert wrote: > >>> Baho Utot <baho-utot@columbus.rr.com> writes: > >>> > >>>> On 02/16/17 06:08, Luca Pizzamiglio wrote: > >>>>> I'm looking for constructive critics, feedbacks, anything that can > >>>>> help me to make portmaster an actively maintained and used tool. > >>>> > >>>> If you can have it build in a clean chroot or jail then you'll get my > >>>> attention > >>> > >>> What kind of special support? > >>> > >>> I use it with a chroot that mounts /usr/ports (and src) read-only, and > >>> aside from the initial base system install, it took about fifteen > >>> minutes to set up. > >>> > >> > >> Using chroot or jails to build each individual package > >> [...] > > > > 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. Hello. You shouldn't have any difficulty accomplishing your goal by simply setting up a jail, and using portmaster within that jail(8). portmaster really doesn't care where it's run. So long as it has everything it needs to accomplish it's job(s). :-) HTH --Chris > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ffa861978cdb1a06a69d7b9af525ad5>