On Fri, 2006-09-29 at 19:37 +0200, Ralf S. Engelschall wrote: > On Fri, Sep 29, 2006, David M. Fetter wrote: > > > Will the openpkg fix be MFC'd into the 2.20060622 stable release as an > > UPD? It would be nice if it was. > > Hmmm.... no, I don't think we should MFC it to the old 2-STABLE > snapshot. Mainly because I've already not MFC'ed other similar things > (like the SetUID) which could too easy break. But we'll MFC it to the > 2-STABLE branch and this way it will be part of the forthcoming 2-STABLE > snapshot which will be rolled around the 18th of October. Have a look at > http://www.openpkg.org/project/events.php for details on the forthcoming > events.
Ah. Well, this brings up another topic. We're finally getting around
to updating our servers from 2.3 to 2-STABLE. However, I'm finding that
some of the logic in the various scripts I wrote to deal with how we
push out and maintain our rpm repository are going to be broken now.
You see, I have some variables that are defined by grabbing the version
based on what 'openpkg -v' spits out. With the new 2-STABLE it seems
that there isn't as nice of a way to display a static version to build
off of. Perhaps I should go into more detail. Since we don't want to
have all of our servers rebuild all rpms, we have our own custom binary
repository setup. The names of this repository has typically been
"${VERSION}-${ARCH}". These variables are obtained via my scripts which
ultimately make this to be something like "2.3-sparc-sun-solaris2.9",
etc. With the way that openpkg now spits out it's version, it means
that all snapshots of 2-STABLE, regardless of when they were made, will
come out to be something like "2STABLE-sparc-sun-solaris2.10", etc.
However, this won't change from snapshot release to snapshot release
using the same method. I can't just grab the date from the way the new
version either because that date changes if the main openpkg rpm has a
UPD rebuild. We need to have something truly static with minimal
changes to overall architecture to ensure production quality. I'm
thinking that there are several ways to resolve this. Is there another
way to get a version of the snapshot time that will stay consistent
throughout changes/updates (i.e. 2.20060622 would work)? If not, can
openpkg -v instead reply with something more like OpenPKG-2.20060622
(2.20060818) so that it shows the snapshot date and next to it the UPD
rebuild date? Mainly, if I had some consistent way to get the snapshot
date so I can setup the binary repos using that, then that would work.
> Ralf S. Engelschall
> [EMAIL PROTECTED]
> www.engelschall.com
>
> ______________________________________________________________________
> The OpenPKG Project www.openpkg.org
> Developer Communication List openpkg-dev@openpkg.org
>
--
David M. Fetter - Portland State University - UNIX Systems Administrator
"Reality is merely an illusion, albeit a very persistent one." ~Einstein
signature.asc
Description: This is a digitally signed message part
