Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Feb 2024 23:23:36 +0900
From:      Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
To:        ports@freebsd.org
Subject:   Re: FreeBSD ports community is broken
Message-ID:  <20240218232336.6a0b6d2a952539aef9d5ebed@dec.sakura.ne.jp>
In-Reply-To: <CAGBxaXki7qDZJ%2BoE4tp06riH6S2bZ=oj9gqPn94-ztBgoj2QTg@mail.gmail.com>
References:  <20240218015843.34c5d078@rimwks.local> <7q6ep7m2eee6yqtxftlwkhuwdkssd74vjow55txms7lkokazfu@grrqllhefges> <20240218174921.a8082649142dd43a469bebfa@dec.sakura.ne.jp> <4ekno7iwxvdlw4xeholcrxuuazmcstxkqyidrz27ni43lzu6wg@3ro6r5b2vhoi> <CAGBxaXnBTF=-V55pbQNJ5czRihAOZvAt53UNzzYT=bgBiqwQ0w@mail.gmail.com> <CALH631kcLJ9KFREovOQXmcbTi1Mbj_dCQuhBqLX%2BPbO6gKJj_w@mail.gmail.com> <CAGBxaXm0PsZRaJsPRxBTyAMxMhe%2BOU_cWErenm-upP0k0=thew@mail.gmail.com> <CALH631kN4bsrDUy1Jr05DQYZOWL=d1emF_Ca1SvNGLeFdfA6wg@mail.gmail.com> <CAGBxaXkuyC8pPQ1qF=LpLwzyo2sD2tBSM2KeVO%2BqJ_G-2pPo0g@mail.gmail.com> <CALH631m%2Boxn1OFAeZifWOHK_GzFtusK8j1MMVaBNnefmDvC4Mw@mail.gmail.com> <CAGBxaXki7qDZJ%2BoE4tp06riH6S2bZ=oj9gqPn94-ztBgoj2QTg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Feb 2024 06:47:25 -0500
Aryeh Friedman <aryehfriedman@gmail.com> wrote:

> On Sun, Feb 18, 2024 at 6:45 AM Gleb Popov <arrowd@freebsd.org> wrote:
> >
> > On Sun, Feb 18, 2024 at 2:35 PM Aryeh Friedman <aryehfriedman@gmail.com> wrote:
> > > No it is not possible since the pkg's are usually of a different
> > > version then what is built from ports (ports is almost newer)
> >
> > There can't be any other way - ports are building recipes for
> > packages. Packages will always lag behind.
> >
> > > may or may not work if your port expects the latest versions.   In
> > > case you have tried it, is it almost impossible to keep a hybrid
> > > pkg/ports machine working your forced to pick one or the other and if
> > > your maintainer then your forced into ports only.
> >
> > If you're using ports only then you still compile everything. I fail
> > to see how this is Poudriere's fault.
> 
> It is Poudriere fault because the default config is completely in
> appropriate for anything smaller then a great builder in the sky
> machine (aka mere mortals).   The defaults for portmaster and make
> install work very well on all machines though.

Adding option "-S" for poudriere significantly reduces build time,
at the cost of risks of possible insanity.

When any port which is required by some ports and forces its consumers
to be rebuilt after upgrading is upgraded, if all (including optional)
consumers are bumped, there's no difference. But if any of consumers
are not bumped, it would NOT be rebuilt with "-S" option, while without
"-S" forces all consumers to be rebuilt regardless they are bumped or
not.

But if lang/rust[-devel] and/or relatively heavy consumers are upgraded,
it wouldn't help. With my experience, rustc EATS UP ALL CORES
INCLUDING HTT CORES EXISTINGG and the computer becomes unresponsive.

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240218232336.6a0b6d2a952539aef9d5ebed>