[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pkg-perl TODO: SVN, archive, upstream, etc versions



On Wed, 25 Jul 2007 17:12:05 -0500, Gunnar Wolf wrote:

> > The result is at http://pkg-perl.alioth.debian.org/qa/versions.html
> _Very_ nice list. I'll be playing a bit (sooner or later... You know
> how I am, I tend to leave things for later :-/ ) - I think adding a
> link here and there can be a good extra :)

Yup, might be nice.
I suggest that if you like to hack on it you ignore the ugly bash
script and go directly to Damyan's rewrite of it in Perl (also in the
scripts directory in svn) which is not completely finished AFAIK but
has more potential :-)
 
> > Similarly with packages claiming to be higher than the upstream -
> > perhaps debian/watch points to some old location.
> AFAICT, we will have to learn to live with some spurious files here
> and there... Maybe we should add something +- like overrides (probably
> bound to a specific version) just so we don't clutter the display with
> what we are already aware of.

At least I can leave with the "known suspects", there are not many
anyway.
 
> > (...)
> > The script is run daily and spends less than a minute on alioth.
> Wow, that's amazing! And... Compared to the DEHS, it does not complain
> as much about not being able to contact the servers.

That was Dam's improvement to check against the CPAN module list
(downloaded once) if possible instead of doing HTTP requests for each
package.
 
> > I guess after fixing (2), this more-or-less provides the functionality
> > of the "pending/" branch we discussed. That is, packages needing an
> > upload are those whose SVN and archive versions differ. Suggestions how
> > to make this more visible on the page are welcome.
> Yes, my only problem with this is the daily frequence - Of course, I
> don't want to tie up Alioth checking upstream versions... But it's not
> good for coordinating work anymore. It's not good to know if you and
> me are doing the same work twice.

I was thinking about a script that could check the status of a single
package (to be run locally) -- or simple a command line parameter to
versioncheck{,-html,.pl} to run it only for one package.
 
> > CAVEATS
> > The script still considers "0.2200" and "0.22" to be different.
> Well, those version numbers are different as per Debian's standards,
> but the same as per CPAN's. Maybe we should interpret them differently
> according to each column? ;-)

That doesn't make comparisons easier :-)
 
Cheers,
gregor 
-- 
 .''`.   http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4
 : :' :  debian: the universal operating system - http://www.debian.org/
 `. `'   member of https://www.vibe.at/ | how to reply: http://got.to/quote/
   `-    "Rome wasn't burned in a day. " 



Reply to: