ptions
/usr/local/etc/poudriere.d/FBSDFSSDjail-options/devel_llvm80/options
/usr/local/etc/poudriere.d/FBSDFSSDjail-options/devel_llvm90/options
/usr/local/etc/poudriere.d/FBSDFSSDjail-options/devel_llvm10/options
/usr/local/etc/poudriere.d/FBSDFSSDjail-options/lang_gcc10/options
The area is separat
riere in that regard?
Gentoo Linux with portage has "--with-bdeps=y" which installs build
dependencies when desired.
I found that poudriere uses dialog4ports; I much prefer to save options in a
file such as Gentoo Linux does with make.conf and (NetBSD) pkgsrc does with
mk.conf .
I once
On 2020-06-14 09:10, George Mitchell wrote:
> I do package builds on one machine on my (small) network, using
> portmaster, and then distributes the built packages to my other
> machines. Last week, I decided to make python38, rather than
> python37, my default version on Python 3. Specifically,
Hi!
> I do package builds on one machine on my (small) network, using
> portmaster [...]
[...]
> And how do I bandage up the foot I shot myself in?
I understand it might be unpopular, but the preferred way to get
to stable updates in the ports tree is using poudriere to
build the ports and the pk
I do package builds on one machine on my (small) network, using
portmaster, and then distributes the built packages to my other
machines. Last week, I decided to make python38, rather than
python37, my default version on Python 3. Specifically,
portmaster -o lang/python38 python37
I think I mis
