blob: e02bd38b84e74fccae12f45837accf03876a0e0b (
plain) (
tree)
|
|
On Tue, Jul 14, 2009 at 5:11 PM, Chris Ball<cjb@laptop.org> wrote:
> > I agree that's a problem. I think the solution is to start making
> > releases, with specific version strings, as source tarballs.
>
> I'm happy to do this if people think it would be useful, and I don't
> yet have a strong opinion on whether the releases should come with
> version numbers or timestamps.
as an user of be that plans to try and "package" it for openembedded,
a release would be very useful: writing a recipe that downloads a
specific commit from bzr and builds it is probably feasible, but
definitely not ideal.
I also have a weak preference for version numbers, as long as they
give useful informations on the state the release.
--
Elena ``of Valhalla''
email: elena.valhalla@gmail.com
_______________________________________________
Be-devel mailing list
Be-devel@bugseverywhere.org
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
|
