On Jun 29, 9:44 am, Paul Miller <[email protected]> wrote: > On Jun 29, 12:28 pm, Dustin <[email protected]> wrote: > > > If I were to make dist right now, it'd look like this: > > > memcached-1.4.0-rc1-3-gd7c78ce.tar.gz > > memcached-1.4.0.tar.gz > > This is all very cool and everything, but the challenge isn't building > the tarball on the dev's machine -- that's a builtin on most of the > Perl package mechanisms. I believed Brandon's thread was about the > auto tarballs on github: > > http://github.com/jettero/mrsh/tarball/2.0203 > > The URL is nice, but the actual file it produces is just the long- > commit-id. > > PAUSE requires a fairly specific filename format. It can take quite a > few styles, but the commitids seem to screw it up.
So then that's the problem at github. There's no reason at all to have a commit id in the path when git describe creates a human- readable and unique identifier for a point in the commit graph. The example that I gave re: memcached has little to do with dev builds. If all github did was use describe to figure out if it could come up with a better name than a commit ID, they'd line up exactly with our dist releases with no further coordination. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
