Date: Mon, 17 Dec 2018 12:15:12 +0100 From: Stefan Esser <se@freebsd.org> To: George Mitchell <george+freebsd@m5p.com>, freebsd-ports@freebsd.org Subject: Re: thunderbird build error Message-ID: <06132b0d-beee-c7d4-df37-39494de61d25@freebsd.org> In-Reply-To: <8d27870a-db54-130a-7210-e4716411770b@m5p.com> References: <9633ff85-0cbb-7e4f-0e6f-62af5478da83@m5p.com> <e2122db0-1945-7628-be3f-54484b1831de@m5p.com> <20181216160715.GA931@phouka1.phouka.net> <e64804fd-38ad-aa55-dc03-1dd83d051128@freebsd.org> <8d27870a-db54-130a-7210-e4716411770b@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--1k1hZl4BlNUrmu5EUe0E0euT4d3WFDPz0
Content-Type: multipart/mixed; boundary="zUceg4TxoOmMAS57sSz56K6Rb0t2R4P5n";
protected-headers="v1"
From: Stefan Esser <se@freebsd.org>
To: George Mitchell <george+freebsd@m5p.com>, freebsd-ports@freebsd.org
Message-ID: <06132b0d-beee-c7d4-df37-39494de61d25@freebsd.org>
Subject: Re: thunderbird build error
References: <9633ff85-0cbb-7e4f-0e6f-62af5478da83@m5p.com>
<e2122db0-1945-7628-be3f-54484b1831de@m5p.com>
<20181216160715.GA931@phouka1.phouka.net>
<e64804fd-38ad-aa55-dc03-1dd83d051128@freebsd.org>
<8d27870a-db54-130a-7210-e4716411770b@m5p.com>
In-Reply-To: <8d27870a-db54-130a-7210-e4716411770b@m5p.com>
--zUceg4TxoOmMAS57sSz56K6Rb0t2R4P5n
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Am 17.12.18 um 00:11 schrieb George Mitchell:
> On 12/16/18 5:24 PM, Stefan Esser wrote:
>> [...]
>> I have (my version of) portmaster mostly working in a clean chroot jai=
l.
>> It is still a pure shell script (works with the FreeBSD /bin/sh and ba=
sh),
>> thus portable to all architectures supported by FreeBSD (e.g. ARM).
>>
>> There are a few edge cases that need further work, but my version does=
>> already support 4 build modes:
>>
>> 1) direct build ("classic portmaster mode")
>>
>> 2) delayed installation (only BUILD_DEPENDS are immediately installed,=
>> all other ports are installed or upgraded from saved packages at th=
e
>> end of the portmaster run)
>>
>> 3) jailed build (everything is built in a chroot jail and installed af=
ter
>> all builds have finished, except for pure build dependencies, which=
are
>> only kept as packages for use in the next portmaster run)
>>
>> 4) repository mode (packages are saved and at the end the repository f=
iles
>> are updated to allow local and remote upgrades with "pkg upgrade")
>> [...]
>> My goal is to have portmaster build everything, but with some restrict=
ions
>> compared to poudriere (only for the architecture and release of the ba=
se
>> system) and with the option to use the direct mode for simple cases an=
d
>> jailed builds (which require extra disk space for the chroot jail) in =
case
>> the builds need to be performed in a clean environment.
>>
>> Regards, STefan
>> [...]
>=20
> Wow! I've been using "classic" mode and I didn't even realize the
> new modes were there. THANK YOU for all your fine work! -- George
Well, they are in my development version, not the one currently in
ports ...
I have worked on the portmaster rewrite since december 2017, when I
noticed that it was impossible to make the current port fully work
with flavors and complex dependency changes. It works for most simple
cases, but there have been changes (e.g. KDE4->KF5) where the current
version just can't pass the required state around (and that could not
be fixed without a lot or effort).
Anyway, I'm giving the current "beta" of the new portmaster to interested=
developers, but there are still a number of details that need to be
cleaned up.
One of the nice features that are already working well is that a failed
portmaster run can be restarted with just "portmaster -R". All state and
options are read in from a restart file (but it is possible to add e.g.
an -x option to exclude some port that causes the failure from the curren=
t
run when restarting ...).
I had hoped to have finished the current version to a state that could
be released at least as portmaster-devel for interested parties to test,
a few months ago. But I have continued adding features (for example to
build the ports in a chroot jail), and I'm alternating between adding
features and cleaning and speeding-up the code ...
I'd really hope to commit that version as an alternative to the current
portmaster port within the next weeks (but I'm not sure that I'll have
much time to work on it over the holidays ...).
Thanks to all that have supported my work by testing draft versions and
who have given very valuable feedback!
Best regards, STefan
--zUceg4TxoOmMAS57sSz56K6Rb0t2R4P5n--
--1k1hZl4BlNUrmu5EUe0E0euT4d3WFDPz0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAlwXhUAACgkQR+u171r9
9USzNwgAiWyEJoluqgM2iN16o143F2zt5ImFtx9VOPbykBVLUEIJ8WJZM1qINrV5
Z1BeQgHhjteBJV61fzGbj9tBGyQi0z8Rg7I7Fh9mZX5Fyr1zT0GArSUqNwggRYS4
nif1doZMRxbHnN1HdbdZxUIYSZ+zAk2vRnt7ulfOL7MbV+IezmJ29sLVkvjpz5VX
XjSskzqcUdTMXzUJJXLW7nYFwyLs2A2X1ijcBjRMnVwkSIF+7yknyKIELt8gREAV
rs64p4YnKzlpF5jQ8Q2v1lQUKC5FOByeIfAZ6LjyYOo039wJAs2uVzIPfNSkI5p5
sTEthlS1ckXmxAlMcidRb9WUk7D2Hw==
=/VRR
-----END PGP SIGNATURE-----
--1k1hZl4BlNUrmu5EUe0E0euT4d3WFDPz0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?06132b0d-beee-c7d4-df37-39494de61d25>