Hi,
Re putting it in darcs, I guess it does or will allow repeated syncs from
a git repo to a darcs repo? If so, you can imagine people starting to rely
on it for synchronisation and being upset it the behaviour changed in a
non-backwards compatible way. I think we do have some responsibility to
maintain backwards compatibility in darcs itself.
Regarding the ongoing maintenance, I'm quite attracted to the idea of
accepting it for maintenance by the darcs team, but with a somehow lower
status than darcs itself. Rather than having a single darcs-contrib bucket
for such things, I'd suggest it just be a separate package on hackage of
its own. I'm also in no rush to add the loose coupling to darcs itself
that you suggest, because I'd prefer it to be clearly separate.
I don't feel very strongly about this, but if we do put it into darcs I am
quite keen on spending some time making sure it works in a way we're happy
with and that has a reasonable degree of future-proofing.
Ganesh
On Wed, 11 Aug 2010, Petr Rockai wrote:
Hi,
so there are two things to consider. While I don't have strong opinions
about whether this should be internal or external, I am a bit concerned
about costs of making these external. Most specifically, I am a bit
overburdened with maintenance tasks already, and I don't want another
package added to that. So I see two options:
- We create a team-maintained "darcs-contrib" hackage package, which
will contain various darcs-foo programs. We can make darcs call those
programs when darcs foo is specified, maybe. Not sure about how help
would be handled etc. Maybe we can really require ~/.darcs/plugins to
describe any plugins that the user wants to use, and they can run
darcs --register foo or something. Nevertheless, I am not exactly
volunteering to do all that work.
- I keep working the conversion code, but someone else takes over
packaging and UI. If there are interested parties, that is.
(The third option is to just accept this to darcs itself. I don't see
any strings attached. We aren't bound to keep this working the same way
forever, it's not even part of the core functionality. Whether it's the
darcs binary or some-other-binary.)
Yours,
Petr.
Eric Kow <b...@darcs.net> writes:
That's a good question and actually it's a very nice thing for Grumpy
Old Men to point out (the possibility of creating an external
application).
Personally, I'm attracted to the idea of some sort of darcs-convert
application, although I can see why it would be particularly
convenient/compelling to have this in Darcs proper. Note also that this
discussion may tie into the plugin system proposed in issue1504.
_______________________________________________
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
_______________________________________________
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
