Re: Crush 2.0 abandoned
Just a short note --
As this discussion moves forward I want everyone to be as clear as they can in describing their ideas, recommendations, and advice in a way that allows us all to appreciate and understand what is being said.
To that end, I'd like to propose/ask we structure the discussion to first answer these questions.
1) Please list the items in order of important and priority (using Neil's item numbers)If possible, I'd like to ask everyone to avoid comments or any debates on philosophical issues or comments express personal preferences. There will be ample time here and elsewhere to debate and discuss those issues at length. At the moment, we need to clarify in as objective a manner as we can where things stand and how to address them in some order of importance.
2) Identify (again by number) what other item(s) on Neil's list either depend on or are affected by that item
3) Explain/detail a possible approach or solution to the item giving a brief answer to the basic questions (who, what, how, why..etc.)
4) Briefly if you disagree with a priority suggestion or can suggest a better solution or approach for an item, please explain your solution or approach and then add comments explaining why its an improvement over the other one.
Thanks again to everyone who has weighed in here so far.
On Thu, Aug 6, 2009 at 5:53 PM, Neil Williams <firstname.lastname@example.org>
On Thu, 6 Aug 2009 18:23:51 +0200
> Hi,Yes, me. I don't want to use git for anything. Subversion is the only
> > > > Get dpkg-cross merged into dpkg as soon as multiarch is supportable.
> > Outlined above.
> BTW, anyone have any strong feelings about moving dpkg-cross repo from CVS
> to git?
real option if you want me to still work with dpkg-cross and you want
to move from CVS. Sorry. I detest git and refuse to use it. dpkg-cross
is trivial, it doesn't warrant the overkill of a system designed for
massive projects like the Linux kernel. IMNSHO git is being abused by
overuse with projects that just don't warrant such a tool. TBH, I don't
see that CVS is that much of an issue for dpkg-cross, there is very
little left to do in dpkg-cross before it is migrated into dpkg.
There is already an old version of dpkg-cross in Emdebian SVN, it only
needs to be brought up to date with current CVS and then declared in
debian/control VCS fields.
I don't think we need to alioth setup anymore, dpkg-cross >= 2.0 is
really an Emdebian-only thing - it certainly will need to be to be
merged into dpkg and dpkg-dev. True, the merge itself might be easier
via git but the final steps need to be done in CVS/SVN and then you can
use whatever tool you like to accomplish the actual merge but I don't
think it's worth making changes in dpkg-cross using git. The merge
should be after the final, final, final release of dpkg-cross. (The
merge won't happen until after multiarch is working anyway.)
It's fairly pointless changing the tool at this stage of the life of
dpkg-cross, that is why I didn't complete the change from CVS to SVN.
It wasn't worth it.