On Sat, Sep 13, 2003, Matthias Kurz wrote: > On Sat, Sep 13, 2003 at 07:56:54PM +0200, Ralf S. Engelschall wrote: > [...] > > > - What criterias does one have to use to decide what version of OpenPKG > > > is required (openpkg >= 20020206, or what) ? > > > > For this there is the HISTORY document in the "openpkg" package > > source tree. It lists all releases of "openpkg" together with a small > > description what happended. We use this as our reference for "openpkg" > > dependencies. > > Cough. ... Cough. ... May i step in, here ? I do not depend on it, but > could you find a better place to flag contributions than just the CVS log ? > A separate document will become a maintenance nightmare and is very likely to become out of sync quickly. But wait - good news. We also have a neat web page that lists it. See http://cvs.openpkg.org/getfile?f=openpkg-src/openpkg/HISTORY :-) Additional information can be found using the timeline feature, see http://cvs.openpkg.org/timeline?x=1&c=2&dm=1&px=openpkg-src/openpkg
This version check should be easy for a RELEASE. For CURRENT, i agree, it is a more complex task to find out the ultimate version. There is a pragmatic approach to this. Just take the openpkg version you used when you created the package. Those who run CURRENT (often have to) upgrade frequently. So your package might just be another trigger to force them to stay up to date. Don't take this version check too seriously. On the CURRENT track it might also happen that a feature changes in a incompatible way or completely disappears and the "greater than or equal to" check will be void anyway. -- [EMAIL PROTECTED] Development Team, Operations Northern Europe, Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
