| non port: Tools/portbuild/scripts/dosetupnode |
|
SVNWeb
|
Number of commits found: 18 |
|
Sun, 24 Apr 2011
|
[ 16:37 flz  ]  (Only the first 10 of 72 ports in this commit are shown above.  )
Remove portbuild scripts from pcvs, as they now live in svn/projects.
|
|
Sun, 23 Jan 2011
|
[ 02:26 linimon ]
Force the copy of portbuild.* files as files, not symlinks. Adjust
the comment for bindist-* to match.
Feature safe: yes
|
|
Thu, 9 Dec 2010
|
[ 00:50 linimon ]
common.conf has to be copied over as well as client.conf.
|
|
Fri, 25 Jun 2010
|
[ 23:21 linimon ]
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
|
|
Thu, 21 May 2009
|
[ 16:17 pav ] (Only the first 10 of 17 ports in this commit are shown above. )
- Update to reflect a reality on pointyhat
|
|
Sat, 26 Jul 2008
|
[ 15:00 kris ]
* 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 (Only the first 15 lines of the commit message are shown above )
|
|
Sun, 29 Jul 2007
|
[ 19:39 kris ]
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.
|
|
Sun, 18 Feb 2007
|
[ 09:03 kris ]
Default to -nocopy when using -norsync
|
|
Fri, 3 Feb 2006
|
[ 20:10 kris ]
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.
|
|
Fri, 27 Jan 2006
|
[ 22:40 kris ]
Don't try to rsync docs, we no longer need to distribute them
|
|
Sun, 11 Dec 2005
|
[ 04:33 kris ]
Don't set -nocopy when -norsync is set, otherwise the setupnode script
doesn't completely prep the client.
|
|
Tue, 11 Oct 2005
|
[ 03:55 kris ]
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
|
|
Sun, 3 Apr 2005
|
[ 04:37 kris ]
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.
|
|
Sat, 12 Feb 2005
|
[ 03:39 kris ]
Only try to chown the portbuild directory if we are a disconnected client
(i.e. it is not mounted by nfs)
|
|
Tue, 28 Dec 2004
|
[ 05:50 kris ]
* 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
efficiently.
|
|
Thu, 25 Nov 2004
|
[ 00:07 kris ]
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
|
|
Mon, 25 Oct 2004
|
[ 04:36 kris ]
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.
|
|
Sun, 26 Sep 2004
|
[ 22:09 kris ]
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)
|
Number of commits found: 18 |
As an Amazon Associate I earn from qualifying purchases.