Re: Testing ports of rust software w/o building rustc

> ----------------------------------------
> From: Paul Mather <paul@gromit.dlib.vt.edu>
> Sent: Fri Nov 11 22:48:31 CET 2022
> To: Nicolas Herry <beastieboy@beastieboy.net>
> Cc: Fernando Apesteguía <fernando.apesteguia@gmail.com>, User Questions <freebsd-questions@freebsd.org>
> Subject: Re: Testing ports of rust software w/o building rustc
> 
> On Nov 11, 2022, at 3:23 PM, Nicolas Herry <beastieboy@beastieboy.net> wrote:
> 
> > Paul Mather <paul@gromit.dlib.vt.edu> writes:
> > 
> > Then I'm curious now: why not opt for poudriere-devel (and binary
> > downloads)? Do you need to pass specific options to the compilation of
> > Rust?
> 
> Also, TBH, the documentation on binary package downloading support in Poudriere isn't exactly extensive.  Prompted by your message I went looking for it and all I could find is some comments at the end of the poudriere.conf.sample file.  (Also, also, I'm running -STABLE, and I don't believe there is a FreeBSD package repo for that, so I don't know how useful the capability would be to me.  I could be wrong, though.)

There's this in poudriere-bulk (8):

     -b branch
              Fetch binary packages from a binary package repository instead
              of building them.  The branch argument can be one of the
              following: latest, quarterly, release_X (where X is the minor
              version of a release, e.g., “0”), or url.

              With this option poudriere will first try to fetch a binary
              package from the specified binary package repository.

              poudriere will only use packages that:
              •   come from a repository having the same or older version of
                  pkg.
              •   do not have a locally fetched package already.
              •   are not IGNORED.
              •   match the expected local version.
              •   match the expected ABI.
              •   match the expected runtime and library dependencies.
              •   match the expected OPTIONS when CHECK_CHANGED_OPTIONS is
                  enabled (default: on).
              •   is NOT listed in PACKAGE_FETCH_BLACKLIST.
              •   is NOT listed with -C, or -c, when -t is used.
              The -v flag can be used to show these decisions during build.
              Specifing twice will show more details on why some are skipped.

              WARNING: poudriere has no way of determining differences outside
              of the above list.  That is, if the local ports framework, or
              port, has custom patches or special WITH_FOO knobs (not OPTIONS)
              then it is required to add its name into
              PACKAGE_FETCH_BLACKLIST.  Otherwise a package may be fetched and
              used that lacks the custom patch or knob.

              See PACKAGE_FETCH_BRANCH, PACKAGE_FETCH_URL,
              PACKAGE_FETCH_BLACKLIST, and PACKAGE_FETCH_WHITELIST in
              poudriere.conf.sample.  The entries in the lists will be matched
              against package names without versions.

The `-vv' option shows the internal logic poudriere uses when analyzing available binaries.


-- 
Sent with https://mailfence.com  
Secure and private email