On 25 Aug 2010, at 13:09, Eric Kow wrote:
On Mon, Aug 23, 2010 at 19:04:18 +0300, Dan Pascu wrote:
If get is supported, shouldn't then push/pull also be supported?
Otherwise interaction with the repo will not be possible past the
initial checkout.
The new Darcs would essentially be forcing you to upgrade to hashed.
As Guillaume says, we could include Darcs 2.5 as part of our phase-out
plan. As far as I can see, there may be a danger of repeating the bad
experience of Darcs 2.0.0 (everybody is scared to upgrade), but maybe
that's not so terrible?
With few responses on this thread, I'm getting the impression that
there
is more enthusiasm about moving on, and few reservations about
deprecating old-fashioned repositories than I'd anticipated. Is that
really accurate?
My inner hacker would be really enthusiastic about the advocated flame
thrower approach to refactoring, but I'm trying to pretend to be a
wizened old man and restrain him (well, Petr, who would actually wield
such flame thrower with the community's blessing, but one can always
flame throw vicariously). If the message really "let her rip!", it
sounds a bit too good to be true.
Is there something we've missed?
This doesn't really address the point I raised. If all you care is to
force people to upgrade (not that you can do that, people will keep
using old binaries if needed), you already can do that today by using
'darcs optimize --upgrade'.
If you still support get from old repos, but nothing else, that will
not motivate people to upgrade, but will create weird situations that
will make darcs look buggy or not well designed. For example:
darcs get old_format_repo_url
# old repo has some new patches recorded
darcs pull old_format_repo_url # fails
# make some local changes
darcs push old_format_repo_url # fails
The user impression is that darcs is failing and there is some support
for the old format, but very incomplete.
IMO, if you support get, then you should also support interacting with
the old format (push/pull). Else, if all you intend is to provide an
upgrade path, then remove any interaction with the old format, except
for 'darcs optimize --upgrade', which will provide the only upgrade
path and users won't wonder why they can get from an old format repo,
but can't pull later some new patches that were added there.
--
Dan
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
