| non port: Tools/portbuild/scripts/updatesnap |
|
SVNWeb
|
Number of commits found: 8 |
|
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.
|
|
Fri, 25 Jun 2010
|
[ 23:42 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.
Several bugs are fixed and improvements are made:
- parameterize everything.
- switch to csup. (This necessitates pushing the repos down one
directory level, e.g. ports-head/ports and src/src-8. However,
this will give us the flexibility to have e.g. src/src-8.1 in
the future.)
- note that the misnomer filename 'cvsdone', which was created
here, is now changed to '.updated'.
Feature safe: yes
|
|
Tue, 22 Jun 2010
|
[ 02:51 linimon ]
Catch up with master copy on pointyhat.
Note: all 3 of these files will be changing radically in the near future.
This is the last checkin from the "classic" codebase installation.
Feature safe: yes
|
|
Mon, 16 Nov 2009
|
[ 00:17 linimon ]
Refactor this to minimize hard-coding. When our support for branches
changes, now you only need to change 2 lines.
|
|
Sun, 8 Nov 2009
|
[ 00:25 linimon ]
Remove dead code.
|
|
Sun, 23 Aug 2009
|
[ 12:20 erwin ]
Add support for RELENG_8
|
|
Thu, 21 May 2009
|
[ 16:15 pav ]
- Separate ports tree updating to use cvsup from cvsup-master instead of cvs
update from NFS mount, which is just way too slow
|
|
Sat, 26 Jul 2008
|
[ 15:16 kris ]
Script run from cron to regularly update the master ZFS copies of the
ports and source trees. Since we have >=1 consumer of these trees
that run frequently but do not insist on up-to-the-second trees, it
makes sense to "pre-update" them regularly and then then re-use in all
of the consumers, instead of potentially doing several updates
simultaneously or on demand. Consumers can clone the ZFS snapshot
into their local filesystem which takes a couple of seconds instead of
minutes or tens of minutes for the CVS update.
We update to a date stamp instead of "." because this avoids
ambiguity of commits that happen while the tree update is in progress
(unfortunately it's slower).
|
Number of commits found: 8 |
As an Amazon Associate I earn from qualifying purchases.