Justin Patrin wrote:
>  On 12/13/06, Gregory Beaver <greg@[...].net> wrote:
> > Christian Weiske wrote:
> > > Hello,
> > >
> > >
> > > It would be really helpful if there was a way to see if commits to CVS
> > > have been made after the latest release. That way you would note if a
> > > package is more advanced in cvs as user, and as developer if you
> > need to
> > > make a new release.
> > >
> > Yes, but how?
> >
> 
>  Well, it could be possible to do a cvs log of all files with the
>  latest RELEASE tag and then look for the current head of each file
>  listed....but this is a PITA and of course wouldn't work for anything
>  not in PEAR's CVS.
In other words, a cron job would have to check out all files, know which
belong to which package (PEAR_Command_Packaging, for instance, is inside
pear-core), and do all kinds of funky stuff to determine whether a file
has been modified.  On the live web server.  It is only possible if we
can get a dedicated server just for this activity, and if we add a lot
more meta-data to the package info, so I won't rule it out, but I will
rule out adding more load to the web server.  As PEAR gets more popular,
we're going to need the extra processing power for more pressing things
like downloads and REST generation etc.
> 
>  With monotone this would be easy. ;-) Just check the head vs the tag
>  for the release and see if the revisions hashes map.
> 
>  With svn this could also be pretty easy. Keep a tag of each revision
>  and compare the tag's creation rev vs the last comitted rev for the
>  package. 

Yes, and with a full time staff of gnomes we could document the entire
PEAR repository in 8 pt Verdana in only 7 days.  It still doesn't make
it possible.

:)
Greg

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php