On Tue, Jul 15, 2003, Matthias Kurz wrote: > When i see it right, the stuff in ftp://ftp.openpkg.org/current/SRC/ > is put together from ftp://ftp.openpkg.org/sources/, isn't it ?
Yes and no. Yes, all parts for the .rpm's in ftp://ftp.openpkg.org/current/SRC/ you should find in ftp://ftp.openpkg.org/sources/{DST,SRC}/. But the .rpm's are not rolled from exactly those files. Technically the direction is the other way round. Instead the .rpm's are rolled from original files on other machines and then a cronjob unpacks the .rpm's on the master server into ftp://ftp.openpkg.org/sources/. Nevertheless you can use the stuff to recreate the .src.rpm's yourself. You then just have one subtle traffic problem: ftp://ftp.openpkg.org/sources/SRC/ you can replace by checking out the openpkg-src/ module from CVS and update this easily directly from CVS. But the ftp://ftp.openpkg.org/sources/DST/ contains a cache of _ALL_ vendor sources, including(!) out-dated versions. So if you want to reduce traffic, this is not the best approach. Because then you have to download even more. Sorry, but that's the price one has to pay for running OpenPKG-CURRENT instead of an OpenPKG-RELEASE version, of course. CURRENT (as the name implies) changes every day and is larger than a release version. > Would it be possible to mirror ftp://ftp.openpkg.org/sources/DST > and ftp://ftp.openpkg.org/sources/SRC (or take this from anon CVS) and > run local commands to build the RPMs ? Pointers ? You can do this by mirroring the stuff via RSYNC, setup a suitable .rpmmacros in your $HOME to point to the dirs and then run "rpm -bs --nodeps" on all .spec files to recreate the .src.rpm files locally. > This way i would not always need to transfer the whole rpm, when > only a comma is changend in the .spec-file. These days (where lots of cleanups and other adjustments are done) certainly a sexy idea. But the best approach usually is to establish a developer/contributor environment with the openpkg-dev script and then just checkout the CVS sources and download the remaining (vendor) files directly from the Internet on demand. This way you reduce your download traffic really to a minimum. I'll try to finally put together a webpage on openpkg.org which documents the various approaches for users, contributors and developers. Sorry that I've still not written such a HOWTO. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
