From owner-freebsd-ports@freebsd.org Fri Feb 17 18:03:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD989CE3835 for ; Fri, 17 Feb 2017 18:03:52 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90EBF18AC for ; Fri, 17 Feb 2017 18:03:52 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: by mail-ot0-x232.google.com with SMTP id k4so16139028otc.0 for ; Fri, 17 Feb 2017 10:03:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=H69/rZNQECT4rnoBGqv9mpkgS++Vi7p0ZaYPOaK1OB0=; b=dc8igAtGfwQ0EdZfk4ibU4jjHV+wbxAGrA8bEj9lYDQKG/ilyimLNmlXcAlbq0kTZb kjlKO4h0yRthr8J7513Zwk6R6IN7huE28phmOsVVzAiXJ1Ah0FqdoDpuBaIyQ+NNgqto D5b7RBE1AEGKxhTgamubu0pFD1RvOU/R7YGw8dHmAbPpq+vavxhP73n7M9mKJcqc0tRN W8NKpvsX1gbmBEOqKyKGH/iZbyRbcaCaKw8Dw+T9EvjWAUGvLa9hbXi+DDOrPl1ldiKM CzPSSpkf9JefOMFifZ9bj3XphbGbnqPXRZy8DMswYHdZSNyuQa7QairBy3jpWQGvUy3O O0IA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=H69/rZNQECT4rnoBGqv9mpkgS++Vi7p0ZaYPOaK1OB0=; b=mfC4jhEbYZccPcOkxs1ge4Kz30ybeT4wVH4MhoDe/EFwMzORZQ3VFXDjY+wQ2bYD+o m+vVXJ6B6BVK2uBRiW+EUUHBf/3YmJd3xFDajPCau1sTau8bczb7m0ivZUgmdgyOpLec WgxdvpIzWJy3f2JXfhKMoPzEXyRbf4UGvM3Sta04OpFvNRgc0Yt/ibx2g+xi1WCr/ADE O5Ip/yv4/luf+OqxJCrj2mJbXnOGQp+VUtCBepdtdQzpMH9bUcA/og0czivdD28djd/1 O0wcnAPTa3qScvXOVfRFSl0gTkGHcOKRHI+39j9iCUKqoJqKOPVxUFFiQfTJnJRdzMff Atlw== X-Gm-Message-State: AMke39loqRRbMjKzidz7atS9M7hFb1oceJ7Z0RzNdXtGBKVoQED7akO4Hv7rChW6mp2UglCk+u6vX3Fii5TGVQ== X-Received: by 10.157.24.43 with SMTP id b40mr4630451ote.212.1487354631617; Fri, 17 Feb 2017 10:03:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.153.226 with HTTP; Fri, 17 Feb 2017 10:03:31 -0800 (PST) In-Reply-To: References: <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> <9ffa861978cdb1a06a69d7b9af525ad5@ultimatedns.net> <8cdf045f-a333-0fcf-c1ab-2fea2114e384@abinet.ru> From: Luca Pizzamiglio Date: Fri, 17 Feb 2017 19:03:31 +0100 Message-ID: Subject: Re: The future of portmaster To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 18:03:52 -0000 Hi all, thanks for all the replies. To summarize: * chroot/jails build could be a nice feature, but it will be an option, not a requirement. I understand the needs to build in a clean environment (poudriere and synth works in this direction for a good reason), but as port maintainer, building in a "dirty" environment detects this kind of configure problems (library auto-detected or auto-enabled) that a clean environment cannot shows. * dropping privileges is really a nice feature to add. The portstree allow you to build everything as normal user, so portmaster can be able to do it as well. * show flags when build fails should be doable * the dependency order is something I'd like to work on, also to improve the internal management I'd like to re-enabling at least --packages-build, that can be really usefu= l. I'll remove: --packages-only|-PP : it looks redundant to me -e : as above, it's redundant; to remove distfiles, --clean-distfiles can be used after a pkg delete I'm also considering to remove, if nobody is using them: * all the --index options, but only * +IGNOREME support (a file saved in /var/db/pkg/ to force ig= nore) No ETA, but I'll do my best. Best regards, pizzamig On Fri, Feb 17, 2017 at 5:55 PM, Chris H wrote: > On Fri, 17 Feb 2017 10:37:16 +0300 abi wrote > >> 17.02.2017 00:22, Chris H =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> > On Thu, 16 Feb 2017 15:48:57 -0500 Baho Utot >> > 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 writes: >> >>>>> >> >>>>>> On 02/16/17 06:08, Luca Pizzamiglio wrote: >> >>>>>>> I'm looking for constructive critics, feedbacks, anything that c= an >> >>>>>>> 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 ge= t 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 o= n >> >> 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). :-) >> > >> From my point of view, jails are overkill. Chroot should be enough and >> it would be nice if portmaster starts building in clean environment. > Oh, I won't argue that. Indeed, chroot(8) is a much lighter solution. > But for my needs, jail(8) is the best solution. As I've already setup > a number for other tasks, anyway. > Speaking of chroot(8), synth(1) chroots all its work. > > All the best. > > --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"