Date: Sun, 19 Feb 2017 14:21:06 -0500 From: Baho Utot <baho-utot@columbus.rr.com> To: freebsd-ports@freebsd.org Subject: Re: The future of portmaster Message-ID: <4ce3635d-4e15-2382-72a6-da94edf57bc7@columbus.rr.com> In-Reply-To: <26956d3b-c91d-fafe-ce2e-0bbdb59e51d2@gmx.de> 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> <26956d3b-c91d-fafe-ce2e-0bbdb59e51d2@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/19/17 10:04, Matthias Andree wrote: > Am 16.02.2017 um 21:48 schrieb Baho Utot: >> 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. >> > > We used to have Tinderbox for the purpose, and now we have Poudriere, > please use that for your purpose. > Portmaster is, by contrast, a tool that focuses on rebuilding a port > using, well, the port in the existing system, > without building a gazillion of requisite other ports for the chroot > first, which easily ends up building some 400 packages when you just > want a convenient way to update ONE port, perhaps with a special > configuration. How about I will use what _I_ find necessary. BTW I am using Synth.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ce3635d-4e15-2382-72a6-da94edf57bc7>