Re: Donation to Foundation for Poudriere /opt builds! (Bounty?)
Sorry, that was the poudriere environment variable. The environment variables used in the jail should be written to /etc/login.conf under the path written in /your_localbase/etc/poudriere.d/jails/*/mnt. There is a path= part in the default entry, so change it. Then run cap_mkdb for its login.conf. The rewriting there is done by function update_version_env in file /your_localbase/share/poudriere/jail.sh, so if you want to automate it, you need to change it. Regards. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Donation to Foundation for Poudriere /opt builds! (Bounty?)
On Tue, Nov 03, 2020 at 07:59:45AM +0900, Tatsuki Makino wrote:
> Perhaps PATH:=${PATH}:/opt/bin
I've tried this in make.conf, and separately PATH=${PATH}:/opt/bin in
poudriere.conf, with LOCALBASE=/opt ; export LOCALBASE in poudriere.conf,
and it dies with this in both cases:
===
===
===> gettext-runtime-0.21 depends on executable: indexinfo - not found
===> Installing existing package /packages/All/indexinfo-0.3.1.txz
[121amd64-2020q4-job-01] Installing indexinfo-0.3.1...
[121amd64-2020q4-job-01] Extracting indexinfo-0.3.1: done
===> gettext-runtime-0.21 depends on executable: indexinfo - not found
*** Error code 1
Stop.
make: stopped in /usr/ports/devel/gettext-runtime
=>> Cleaning up wrkdir
===> Cleaning for gettext-runtime-0.21
build of devel/gettext-runtime | gettext-runtime-0.21 ended at Mon Nov 2
18:32:55 EST 2020
build time: 00:00:37
!!! build failure encountered !!!
I appreciately your help and hope there's more coming. It feels like
something path-related, as I see failures like:
===> swig-4.0.2 depends on executable: lua52 - not found
...but I'm not sure what combination of things I'm missing.
Do I need to builds from straight ports with LOCALBASE set to /opt and get
a Poudriere that can build to /opt that way, or won't that matter? I'm
still somewhat unclear about the interaction of the various variables.
Thanks for the help thus far, and thanks in advance for everyone's help.
PS: If it wouldn't be a huge amount of trouble, I'd love to see someone
with far more clue about Poudriere than I've got reproduce what I'm trying
to do locally, so that we have a better idea if I'm just doing it wrong or
if it's in fact broken. I'm hoping I'm just doing it wrong.
--
Mason Loring Bliss (( If I have not seen as far as others, it is because
ma...@blisses.org )) giants were standing on my shoulders. - Hal Abelson
signature.asc
Description: PGP signature
Re: Donation to Foundation for Poudriere /opt builds! (Bounty?)
Hello.
Mason Loring Bliss wrote on 2020/11/02 23:41:
> This seems not to quite do it. I tried this in make.conf both with and
> without PATH specified:
>
> PREFIX=/opt
> LOCALBASE=/opt
> LICENSES_ACCEPTED+=HPLIP_PLUGIN
> PATH:=$PATH:/opt/bin:/opt/sbin:/testmarker
>
> With the path, gettext-runtime failed with https://bpa.st/SRXA
>
> Without the path, it failed with https://bpa.st/CUTQ
>
> (Both those pastes should persist for a week.)
>
Perhaps PATH:=${PATH}:/opt/bin
PREFIX is set to LOCALBASE by default (somewhere in bsd.port.mk.).
LINUXBASE may rewrite PREFIX (somewhere in bsd.port.mk.).
Hence PREFIX=/opt is too much.
I would write the environment variables in ${PREFIX}/etc/poudriere.conf
shell script :) .
Regards.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What are the benefits of NO_ARCH?
On Mon, Nov 02, 2020 at 03:48:34PM +0100, Stefan Esser wrote: > Am 02.11.20 um 15:33 schrieb Mateusz Piotrowski: > > Hi ports@, > > > > I wonder if setting NO_ARCH=yes brings any significant benefits to how > > our ports collection works. I'd be grateful if you could shed some light > > on the importance of setting NO_ARCH whenever possible. > > NO_ARCH means that there is no need to build packages for each of the > supported architectures, e.g. for pure interpreted scripts or data files > that do not depend on byte-order and word-size (e.g. many font file > formats). > > The result is reduced resources spent on building the packages, network > traffic, disk space on mirrors and on distribution media. > > Regards, STefan Yes that is the goal, in practice it is not yet the case, so it is purely informational, but that what we are aiming at yes. Best regards, bapt signature.asc Description: PGP signature
Re: What are the benefits of NO_ARCH?
Am 02.11.20 um 15:33 schrieb Mateusz Piotrowski: Hi ports@, I wonder if setting NO_ARCH=yes brings any significant benefits to how our ports collection works. I'd be grateful if you could shed some light on the importance of setting NO_ARCH whenever possible. NO_ARCH means that there is no need to build packages for each of the supported architectures, e.g. for pure interpreted scripts or data files that do not depend on byte-order and word-size (e.g. many font file formats). The result is reduced resources spent on building the packages, network traffic, disk space on mirrors and on distribution media. Regards, STefan OpenPGP_signature Description: OpenPGP digital signature
Re: Donation to Foundation for Poudriere /opt builds! (Bounty?)
On Mon, Nov 02, 2020 at 07:47:07AM +0100, Alex Dupre wrote: > I think you should use: > > PREFIX=/opt > LOCALBASE=/opt This seems not to quite do it. I tried this in make.conf both with and without PATH specified: PREFIX=/opt LOCALBASE=/opt LICENSES_ACCEPTED+=HPLIP_PLUGIN PATH:=$PATH:/opt/bin:/opt/sbin:/testmarker With the path, gettext-runtime failed with https://bpa.st/SRXA Without the path, it failed with https://bpa.st/CUTQ (Both those pastes should persist for a week.) -- Mason Loring Bliss ma...@blisses.orgEwige Blumenkraft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I signature.asc Description: PGP signature
What are the benefits of NO_ARCH?
Hi ports@, I wonder if setting NO_ARCH=yes brings any significant benefits to how our ports collection works. I'd be grateful if you could shed some light on the importance of setting NO_ARCH whenever possible. Thanks, Mateusz ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Correct path for man pages
Got it, thanks!
Mateusz Piotrowski <0...@freebsd.org> escreveu no dia domingo, 1/11/2020
à(s) 18:20:
> On 11/1/20 2:41 PM, Nuno Teixeira wrote:
> > I remember reading something about correct path for man pages:
> >
> > ${STAGEDIR}${PREFIX}/share/man/manN
> > or
> > ${STAGEDIR}${MAN1PREFIX}/man/manN
> >
> > Can't find original post about it.
>
> Probably the CHANGES file in the ports tree:
>
> 20200115:
> AUTHOR: b...@freebsd.org
>
>${PREFIX}/share/man is now a valid location for manpages ${PREFIX}/man
> being
>considered as deprecated.
>
> Cheers,
>
> Mateusz
>
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
