Recently, "M.-A. Lemburg"
Jack Jansen wrote:
Could we add a field that would allow for the functionality that is now in the (very little known) checkversion.py script?
Doesn't the Version field have this information ?
The version field has half the info. The other half needed is an easy way to find the most recent version. With a whole file of metainformation it's probably the easiest to just make the current metainformationfile readily accessible on the net (i.e. not only in an installer archive) and make the URL "permanent". Actually the URL doesn't even have to be permanent: if the version 1.0 metainfofile has a URL www.veryoldsite.com/bla/package/metainfo.xml, and that file (for version 2.0) has www.newersite.com/bla/package/metainfo.xml you could keep a chain of the things. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
Jack Jansen wrote:
Recently, "M.-A. Lemburg"
said: Jack Jansen wrote:
Could we add a field that would allow for the functionality that is now in the (very little known) checkversion.py script?
Doesn't the Version field have this information ?
The version field has half the info. The other half needed is an easy way to find the most recent version. With a whole file of metainformation it's probably the easiest to just make the current metainformationfile readily accessible on the net (i.e. not only in an installer archive) and make the URL "permanent". Actually the URL doesn't even have to be permanent: if the version 1.0 metainfofile has a URL www.veryoldsite.com/bla/package/metainfo.xml, and that file (for version 2.0) has www.newersite.com/bla/package/metainfo.xml you could keep a chain of the things.
Good idea. How about a "Metainfo-URL" field which then points to the metainfo file on some web-site ?! (It could default to <homepage URL>/<package name>-metainfo.xml) -- Marc-Andre Lemburg ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Pages: http://www.lemburg.com/python/
On Thu, Mar 15, 2001 at 11:15:15PM +0100, Jack Jansen wrote:
The version field has half the info. The other half needed is an easy way to find the most recent version. With a whole file of
Well, the idea is that once we have this meta-data in a standard format,
it's easy to upload to the catalog server. Then a user could simply
query the catalog server and ask it what the most recent version of
the package is. This prevents (in theory) the problem of the URL
changing after a version has been pushed out...
I've even got the code together for automaticly pushing out the meta-data
file (even if it's simply included in the sdist tar file) to the catalog
server.
Sean
--
Put out fires during the daytime. Do your real work at night.
Sleep is just an addiction. -- Dieter Muller
Sean Reifschneider, Inimitably Superfluous
participants (3)
-
Jack Jansen
-
M.-A. Lemburg
-
Sean Reifschneider