notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
This referral link gives you 10% off a account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: Tools/portbuild/scripts/dosetupnode

Number of commits found: 18

Sunday, 24 Apr 2011
16:37 flz search for other commits by this committer
Remove portbuild scripts from pcvs, as they now live in svn/projects.
Original commit
Sunday, 23 Jan 2011
02:26 linimon search for other commits by this committer
Force the copy of portbuild.* files as files, not symlinks.  Adjust
the comment for bindist-* to match.

Feature safe:   yes
Original commit
Thursday, 9 Dec 2010
00:50 linimon search for other commits by this committer
common.conf has to be copied over as well as client.conf.
Original commit
Friday, 25 Jun 2010
23:21 linimon search for other commits by this committer
Generalize the packge building scripts to be able to be run on more than
one 'head' node, rather than just pointyhat itself.

Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf.  There is
only one server.conf file.  Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.

Add the copying over of client.conf to the clients, and take care
to force the file copy regardless of whether it is a symlink.

Feature safe:   yes
Original commit
Thursday, 21 May 2009
16:17 pav search for other commits by this committer
- Update to reflect a reality on pointyhat
Original commit
Saturday, 26 Jul 2008
15:00 kris search for other commits by this committer
* Cleanup

* Catch up to build ID directory changes

* Support a meta-hostname of 'all' for setting up all clients at once.
  This is better than the old way of running one copy of the script
  for each client by hand, since it is easier and involves less
  duplicated work.

* We copy in the per-build ports, src, and bindist .tbz files and .md5
  checksums, as well as refreshing the build scripts and
  bindist-$(hostname).tar customization tarball.

* The -force switch forces copying of files and re-extraction of the
  tarballs on the client.  This is necessary in order to propagate
  local changes to the tarballs after the initial client setup
  (e.g. if you need to change a file in the ports tree, it must be
  recompressed, redistributed, and re-extracted on the client).

* The -queue switch will poll the client's job queue after completion
  of the setup.  This is racy and should only be used when the machine
  is not currently accepting jobs.

* For cleaning up a build the 'build cleanup' command should now be
  used instead.  It calls back into this command but also allows full
  clenaup of build-local files on the client.

TODO: "all" setups are hard on the server since they may spawn dozens
of rsyncs at once.  A better solution would be to have a worker pool
of setup tasks to limit the maximum load.
Original commit
Sunday, 29 Jul 2007
19:39 kris search for other commits by this committer
Use rsync -L instead of rsync -l to deal with the fact that we like to
symlink ports and src trees elsewhere.  With -l this would turn a populated
tree into a dangling symlink.
Original commit
Sunday, 18 Feb 2007
09:03 kris search for other commits by this committer
Default to -nocopy when using -norsync
Original commit
Friday, 3 Feb 2006
20:10 kris search for other commits by this committer
Don't bother chowning the client /var/portbuild/, it just takes too long
and this doesn't happen in practise unless you screwed up manually.
Original commit
Friday, 27 Jan 2006
22:40 kris search for other commits by this committer
Don't try to rsync docs, we no longer need to distribute them
Original commit
Sunday, 11 Dec 2005
04:33 kris search for other commits by this committer
Don't set -nocopy when -norsync is set, otherwise the setupnode script
doesn't completely prep the client.
Original commit
Tuesday, 11 Oct 2005
03:55 kris search for other commits by this committer
When -norsync is set, don't bother to run md5 over the bindist.tar
and copy it to the client.  This has two benefits:

1) Avoids spamming the master with dozens of md5 processes when
   dosetupnode is spawned for all client machines at ocne

2) Avoids silly copy attempts on disconnected nodes for which the file
   is copied to itself
Original commit
Sunday, 3 Apr 2005
04:37 kris search for other commits by this committer
Change rsync -l to -L for the tarballs/ directory (so that dangling
symlinks are not created on the target) and rsync the entire
directory so that extra files are deleted.
Original commit
Saturday, 12 Feb 2005
03:39 kris search for other commits by this committer
Only try to chown the portbuild directory if we are a disconnected client
(i.e. it is not mounted by nfs)
Original commit
Tuesday, 28 Dec 2004
05:50 kris search for other commits by this committer
* Support the -norsync argument to only remove the existing build chroots
  on a disconnected client, without running the time-consuming rsyncs.
  This is useful when a build is interrupted and needs to be restarted.

* After we have cleaned up the machine, reset the queue counter by using
  pollmachine -queue.  This has a race condition if other builds are being
  dispatched to the machine (e.g. builds on another branch):

  getmachine can claim a directory and increment the counter, then the
  machine is polled and finds e.g. 0 chroots in use, and resets the
  counter to 0, then claim-chroot is run and the build dispatched, with
  the counter now off-by-one.  This could be fixed by running
  claim-chroot with the .lock held, but this turns out to be too
  time-consuming.  A two-level lock approach might also fix this
Original commit
Thursday, 25 Nov 2004
00:07 kris search for other commits by this committer
If sudo_cmd is set, assume we need to chown the files we created on
the client to the client_user so they can later write to them
Original commit
Monday, 25 Oct 2004
04:36 kris search for other commits by this committer
Fix a couple of bugs in the extraction of this from dopackages, and
flatten the setupnode() function into the main body since it's only
called from one place.
Original commit
Sunday, 26 Sep 2004
22:09 kris search for other commits by this committer
Break out the setupnode function of dopackages into a separate script so
that it may be called by hand.

Support new portbuild.conf variables

    client_user = user to connect to on the client (not necessarily
                  root).  This user must have write permission to the
                  /var/portbuild tree if disconnected=1 (i.e. we're
                  going to run rsync).
    rsync_gzip  = set to "-z" to enable compression on low-bandwidth
                  disconnected clients.

Approved by:    portmgr (self)
Original commit

Number of commits found: 18