[arch-dev-public] The move to SVN
aaronmgriffin at gmail.com
Tue Apr 8 03:10:36 EDT 2008
On Tue, Apr 8, 2008 at 12:44 AM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On Tue, Apr 8, 2008 at 12:10 AM, eliott <eliott at cactuswax.net> wrote:
> > wewt!
> I guess I forgot some explanation, huh?
> Jason covered most of it in the old thread, but I will regurgitate:
> The new devtools package (incoming soonish) contains a few real tiny
> tools. The first of these is "archco". You use it to checkout and
> update a single package. Now, you don't have to do this, but a full
> checkout takes some time...
> Anyway, say I run "archco openssh". I then cd openssh/trunk/, make the
> PKGBUILD edits, and commit them. The trunk, however, does nothing.
> It's just the master copy. Now what we do is run "archrelease
> core-i686". Alternatively, I can run "extrapkg" and it will do this
> step for me.
> So then the package is uploaded via extrapkg, and I run the db scripts
> as I used to. However, this time they take a tad longer. The svn
> export is a little more weighty than before. I may change it to use a
> permanent checkout per user (say at ~/.dbscripts/checkout or
> something) to make it much faster, but that's less important than
> actual functionality right now.
> Let me know if I got all this right, and I covered everything enough
> for you all.
Caught a few bugs, the biggest one was on x86_64 (we killed off the
"64" suffix on the staging dirs on accident). devtools 0.6.1 should be
If you happen to use 0.6.0 on x86_64, just know that the package was
uploaded to staging/extra/add, and copy it to the right staging dir.
More information about the arch-dev-public