On 5/30/07, Christopher Hicks <chicks@xxxxxxxxxx> wrote:
On Wed, May 30, 2007 at 12:51:54PM -0700, Chris Weyl wrote:
> :) I'm poking around, trying to see what it'd take to get this into
> either Fedora cvs, or maybe as some sort of a "hosted project". No
> aversions to releasing things as tarballs, but having it in a RCS
> somewhere would make collaboration / patches so much easier.
Sounds good. Thanks for what you've done so far. It is very slick and getting even better.
Thanks!
I just found http://fedoraproject.org/wiki/Infrastructure/ProjectHosting;
hopefully someone on fedora-devel-list will be able to tell me how to
actually invoke the new project process :)
I'm assuming you've noticed that some of the POE package versions are dorked and show as %(rpmver)?
Yeah, um, that's me. The mapping script doesn't actually evaluate
%{version} against the spec file, it simply looks for (V|v)ersion:.
POE modules had this tendency to go from, say, 0.95, 0.96, 0.9601,
0.97... That was my classy way of avoiding epoch's. I'm working to
reset that; it helps the bingos has largely switched to a more
consistent versioning scheme.
Another apparent issue is that we have no idea of what version of the module was current when a given version of fedora froze, but there may be enough module release history for some modules to figure that out. From here out we can just say "this is the version that was on CPAN on freeze day". I'll try to generate the data from backpan this weekend if nobody beats me to it. ;)
Now that would be interesting for some modules -- what version a given
Fedora release started out at vs where it is currently (or ended up
at).
I'm also thinking a "devel not current against CPAN" list/alert would be nice.
Thanks again all around.
No problem. I'm holding you to your patches comment :)
-Chris
--
Chris Weyl
Ex astris, scientia
