{"thread":{"id":"40915","subject":"Dependency query regarding contrib scripts","startedAt":"2015-12-01T16:52:10Z","lastAt":"2015-12-01T20:52:04Z","messageCount":2,"participants":["Richard Ipsum","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"273861","messageId":"20151201165209.GA28230@salo","threadId":"40915","inReplyTo":null,"subject":"Dependency query regarding contrib scripts","fromName":"Richard Ipsum","fromEmail":"richard.ipsum@codethink.co.uk","sentAt":"2015-12-01T16:52:10Z","receivedAt":"2015-12-01T16:52:10Z","isPatch":false,"sender":{"key":"richard.ipsum@codethink.co.uk","avatar":null},"body":"Hi,\n\nHaving read the docs for integrating new subcommands into git[1] I am looking\nfor some clarification of the following,\n\n\"While we strongly encourage coding in portable C for portability,\nthese [C, shell, perl] specific scripting languages are also acceptable.\nWe won’t accept more without a very strong technical case,\nas we don’t want to broaden the Git suite’s required dependencies\"\n\nDoes this also mean that use of non-core modules by, for example, perl scripts,\nis out of the question for contrib scripts? Or is it acceptable but ideally\nminimised?\n\nIn particular I'd like to be able to make use of Git::Raw[2] and also ideally\nthe Moo framework[3].\n\nThanks,\nRichard Ipsum\n\n[1]: ftp://www.kernel.org/pub/software/scm/git/docs/v2.4.0/howto/new-command.html\n[2]: http://search.cpan.org/~jacquesg/Git-Raw-0.58/lib/Git/Raw.pm\n[3]: http://search.cpan.org/~haarg/Moo-2.000002/lib/Moo.pm\n"},{"id":"273874","messageId":"20151201205204.GE18255@google.com","threadId":"40915","inReplyTo":"20151201165209.GA28230@salo","subject":"Re: Dependency query regarding contrib scripts","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2015-12-01T20:52:04Z","receivedAt":"2015-12-01T20:52:04Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Richard Ipsum wrote:\n\n> Having read the docs for integrating new subcommands into git[1] I am looking\n> for some clarification of the following,\n>\n> \"While we strongly encourage coding in portable C for portability,\n> these [C, shell, perl] specific scripting languages are also acceptable.\n> We won’t accept more without a very strong technical case,\n> as we don’t want to broaden the Git suite’s required dependencies\"\n>\n> Does this also mean that use of non-core modules by, for example, perl scripts,\n> is out of the question for contrib scripts? Or is it acceptable but ideally\n> minimised?\n>\n> In particular I'd like to be able to make use of Git::Raw[2] and also ideally\n> the Moo framework[3].\n\ncontrib is its own world.  Your best bet is to ask the maintainer of\nthe relevant contrib script what kind of portability they require\n(cc-ing this list).\n\nIf you are the maintainer, then go wild. ;-)\n\nThanks,\nJonathan\n\n> [2]: http://search.cpan.org/~jacquesg/Git-Raw-0.58/lib/Git/Raw.pm\n> [3]: http://search.cpan.org/~haarg/Moo-2.000002/lib/Moo.pm\n"}]}