With ports-mgmt/synth it is possible to set it to use pre-built packages for dependencies.
With ports-mgmt/synth it is possible to set it to use pre-built packages for dependencies.
I use the "fetch pre-built packages" option in Synth all the time, it sames a fair amount of time, and I am not aware of any consequences from using it.
.... to this glaring oversight in poudriere.
I've never used poudriere myself, but I do know a bunch of the fellows here pretty much insist on building all packages. There are synth users here I do believe that leave that option turned off. Not sure why, it may be what they are used to, personal preference.
Or maybe there is a good valid technical reason that I missed.
poudriere
or synth
or portmaster
or make config-recursive install clean
or pkg
--FreeBSD always only installs binary packages. The difference lies in where those packages come from: a repository of compiled binary packages from FreeBSD (as a collective) or a repository of your own locally compiled binary packages (whether that's a repository of 1 [locally compiled] package at a time via portmaster category/port
or make install
or a repository of many compiled packages from a bulk poudriere
or synth
build). That's the only difference in the two systems of installing programs on FreeBSD. They're all binary packages that get installed.They're all binary packages that get installed.
pkg delete -af
. make install
the pkg() itself is a dependency as it builds and installs first.The stage directory support means that a port does not install directly into the destination directories, but instead into a separate directory (automake packages call this DESTDIR) from which the package is then built - in many cases, this does not require root privileges. If enabled for a port, the package is first built, installed into the STAGEDIR, packaged, and then installed from the package. If disabled, the traditional approach is used, which means to install directly into the destination and build the package from there.
I was sure there was a discussion about this a couple years ago, that portmaster does not create a package that gets extracted and installed. Yeah it creates a binary and does other stuff, but a 'package' is not created. Someone feel free to correct me. Anyone remember that discussion thread ?
postmaster category/port
creates a binary package before installation of the program.No, portmaster uses the install target of the port in that case and it doesn't create an intermediary package. It just creates a package manifest and registers the port installation with the package database (see pkg-register(8)). There is no compression step and no *.txz is being created.I'm not aware of that discussion, but I don't think that's the case; I have packages installed on my system that were installed via portmaster. Pretty surepostmaster category/port
creates a binary package before installation of the program.
-b name Specify the name of the binary package branch to use to prefetch
packages. Should be "latest", "quarterly", "release_*", or url.
With this option poudriere will first try to fetch from the
binary package repository specified the binary package prior to
do the sanity check if the package does not already exist. When
-t is used along with -C, or -c, then listed packages will not
be fetched.
See PACKAGE_FETCH_BRANCH, and PACKAGE_FETCH_URL, in
poudriere.conf.sample.