Bazaar as Subversion replacement
John Whitley
whitley at acm.org
Wed Jan 17 03:45:46 GMT 2007
Nicholas Allen wrote:
> It is the number one show stopper for us.
I'll second that (and the tags and external diff support). Line
ending support is also a showstopper for adoption in my
organization. We need explicit support for multiple line-ending
conventions (DOS and Unix) within one branch.
It would be sufficient to have a pre-commit hook that was guaranteed
to be shared by all users of a branch (e.g. via pre-commit hook code
or file versioned and stored in the branch itself). OTOH, as a
matter of larger Bazaar policy, it seems to be very insecure to allow
an arbitrary branch from-the-wild to run code as a local user (and
unfortunately, Python has no sandboxing to speak of).
FYI, in our current CVS implementation of this, the commit is denied
if the line-ending pre-commit test fails. This test is done on a
pattern-matching basis against the file name. Perhaps a simple,
optional, versioned file akin to .bzrignore that enumerated explicit
line-ending rules would suffice as a first-pass, with something nicer
based on versioned properties available once properties finally come
to pass.
-- John
More information about the bazaar
mailing list