How to keep some ports and many binary packages up to date

marino@
Maybe, it is a bug
But pkg updating -d 20160214 shows nothing, but
Code: 
/usr/ports/UPDATING:
20160214:
  AFFECTS: users of www/nginx-devel
  AUTHOR: osa@FreeBSD.org

  Dynamic modules support has been enabled for the following third-party
  modules, in case of usage of these modules please update nginx
  configuration file for load these modules:
  .......

If someone confirm I make a PR.

Edit: But pkg updating -d 20160214 - work, but I doubt it is the right syntax.
 
daudo said:
* I see that synth produces a separate repository in /var/synth/live_packages/. I guess I this is also intended to be served to other servers?
Click to expand...

A repo can be just for the host or for an unlimited number of clients. Whatever you want.

* And if I see it correctly, you can only build packages/ports for the host OS version where synth is running. Is that correct? Background is that eventually I may have different FreeBSD versions to provide packages for.
Click to expand...

That's not really correct. I've been tweaking it so that it can build packages for other earlier releases (and amd64->i386 i suppose). It should work fine on v1.00. v0.99_7 is almost there but it needs a little more.
 
tankist02 said:
Yes, you can point other servers to the synth repo on the master machine.
If you need to cross-compile then use poudriere.
Click to expand...
cross-compiling isn't the right term; poudriere can't do that either.
As above, synth can build for other releases (e.g. 11.0-CURRENT can build 10.2 packages)
 
marino said:
A repo can be just for the host or for an unlimited number of clients. Whatever you want.
Click to expand...

Thank you for synth. As for pointing clients to the repo on the server, is it as simple as running a web server that points to /var/synth/live_packages/ and then adding the new repo to /usr/local/etc/pkg.conf on the clients?
 
or transfer the contents to a webserver.
A typical solution is have it at the standard ABI, e.g.
http://avalon.dragonflybsd.org/dports/dragonfly:4.6:x86:64/

The clients repo conf might be similar to:
Code: 
Avalon: {
        url             : http://mirror-master.dragonflybsd.org/dports/${ABI}/LATEST,
        mirror_type     : NONE,
        signature_type  : NONE,
        pubkey          : NONE,
        fingerprints    : /usr/share/fingerprints,
        priority        : 10,
        enabled         : yes
}
 
You must log in or register to reply here.
Back
Top