Page MenuHomeFreeBSD

portsnap-build: switch to git
Needs ReviewPublic

Authored by emaste on Wed, Apr 7, 2:48 PM.

Details

Diff Detail

Lint
Lint Skipped
Unit
Unit Tests Skipped

Event Timeline

emaste requested review of this revision.Wed, Apr 7, 2:48 PM
emaste created this revision.

s/describes-icbm.sh needs updating still

build.conf
7–8

I did this for now because world.tar that I created is too large; we should (separately) add some advice on creating world.tar for anyone reproducing this outside of FreeBSD.org. Will not commit with this change.

build.sh
26

Perhaps should set REPODIR=${STATEDIR}/gitrepo in build.conf and use it throughout.

releasesnap.sh
19

Probably need git --git-dir=${STATEDIR}/gitrepo fetch first here too

first take at describes-icbm.sh update

Is it possible for us to run this on a trial bases and have the updates available via e.g. portsnap-git-beta.FreeBSD.org?

first take at describes-icbm.sh update

I'm not too worried about describes-icbm -- worst case people don't get any emails and it takes an hour or two longer for anyone to notice broken dependencies. If you're worried I would just disable it completely for now.

Is it possible for us to run this on a trial bases and have the updates available via e.g. portsnap-git-beta.FreeBSD.org?

If you mean new builds with a new signing key, sure. If you mean with the live keys, I would be a bit worried about causing more problems than we solve by doing that.

If you mean new builds with a new signing key,

Yes, this. Completely decoupled from the current infrastructure so there is no chance of breaking anyone.

If you mean new builds with a new signing key,

Yes, this. Completely decoupled from the current infrastructure so there is no chance of breaking anyone.

No problem at all. I think you've seen how to generate keys? Just set up a web server somewhere which the portsnap builds can upload bits into.

(Unlike freebsd-update, where update-master has encrypted bundles of bits, portsnap-master is just a portsnap mirror -- so there's no need to worry about the master->mirrors side of things here unless you're expecting a huge volume of traffic.)

build.conf
1–2

I believe that to deploy we should be able to copy in existing build.conf and then apply this change.

releasesnap.sh
19

Added locally now