hi emilio, On Thursday 01 November 2007 03:36:14 am Emilio Scalise wrote: > Why the version number still includes ~emiscabpo? I've added that to > differentiate packages from my repository to the official debian ones. > But now they would become official debian packages, this release tag > could be removed. i was thinking that we could remove the tag when the non-cdbs using packages were uploaded. but if you want to remove it in your next version, thats totally fine. we should just come up with some kind of way to differentiate between your versions and mine. how about you start doing simply -N, where n is an incrementing integer, and if i need to make changes in your -N i'll do a -(N+1)~something (otherwise i'll just upload your version directly). > Regarding emerald, compiz fusion folks, haven't released a 0.6.0 > version. They say in the 0.6.0 release announce that > http://lists.compiz-fusion.org/pipermail/community/2007-October/000142.html > "Please note that emerald and the emerald-themes components are being held > until the next release due to a runtime crasher. Emerald 0.5.2 can still > be used > in the meantime." aha. > So we can choose: > * emerald version 0.5.2 > * latest emerald git tree, like I did. > * not include emerald i don't have any particular confidence at *any* release of compiz etc being incredibly stable, so i say it's fine for using git snapshots for the time being, as long as the versioning system doesn't mess up when we switch to a "stable" version. the important thing though is that the packages themselves are in good shape, for whatever version of the code we use. anyway, thanks for your efforts! sean
Attachment:
signature.asc
Description: This is a digitally signed message part.