DragonFly users List (threaded) for 2010-09
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
HEADS UP - pkgsrc.git users - Major changes - pkgsrcv2.git now gtg
DragonFly Users
Ok, the new pkgsrcv2.git repo is up and the old pkgsrc.git repo is
gone. Here is the skinny on it.
New official pkgsrc mirror for DragonFly users:
git://git.dragonflybsd.org/pkgsrcv2.git
UPDATING /usr/Makefile, and updating /usr/pkgsrc:
Your /usr/Makefile needs to be updated. Simply change any instances
of 'pkgsrc.git' to 'pkgsrcv2.git'. You can then use the Makefile
to build your new pkgsrc repo if you desire, or you can follow the
manual instructions below.
You must wipe your old /usr/pkgsrc completely and pull the new
one down from scratch. There is no way to incrementally update
your existing repo. The new repo is ~600MB or so.
You can do it manually as follows:
cd /usr
rm -rf pkgsrc
mkdir pkgsrc
cd pkgsrc
git init
git remote add origin git://git.dragonflybsd.org/pkgsrcv2.git
git fetch origin
git branch master origin/master
git pkgsrc-2010Q1 master origin/pkgsrc-2010Q1
git pkgsrc-2010Q2 master origin/pkgsrc-2010Q2
git checkout master
note: 2.6 users who are still on pkgsrc-2010Q2 might want to
checkout 2010Q2 instead, but if you are already on 'master'
and have used pkgsrc you probably should stay on 'master'
Once your new pkgsrc repo is in place you can keep it up-to-date with
a simple git pull. This is an incremental operation and will not take
much time:
cd /usr/pkgsrc
git pull
EXAMPLE CRON JOB:
Here is an example cron job that will keep your pkgsrc repo
up-to-date on a one-hour cycle once you have completed the
initial checkout. Please be sure to use lockf in case a step
change occurs, to prevent pulls from backing up on your server
(it's amazing to me how few people use lockf to prevent crons
from stacking up!). Randomize the minutes fields (the 25)
please, from 0-59.
25 * * * * cd /usr/pkgsrc; lockf -kst 0 .lock git pull -q
ACCESSING ALL THE PKGSRC BRANCHES
The pkgsrcv2 git repo has only a few selected branches. master,
pkgsrc-2010Q1, pkgsrc-2010Q2, and of course Q3 when it comes out.
People who want access to *ALL* the pkgsrc branches can use a
different repo. The repos can be mixed (commitids and refs are
compatible):
git://git.dragonflybsd.org/pkgsrcm2.git SPECIAL CASE USE ONLY
NETBSD USERS NOTE: Our pkgsrc git mirrors are now generated from the
NetBSD-CVS cvsup, using the fromcvs/togit scripts, on a 6-hour cron
schedule. The commit ids and packs will be COMPLETELY DIFFERENT
relative to the unofficial NetBSD pkgsrc git repo, so you need to
choose your poison.
-Matt
Matthew Dillon
<dillon@backplane.com>
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]