Re: RFC: a plugin architecture for git extensions?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 27, 2011 at 05:36, Jon Seymour <jon.seymour@xxxxxxxxx> wrote:

> What would be call is if I could package my extension in a standard
> way and then anyone who was interested could simply do something like:
>
> Â Âgit plugin install gitwork
>
> and then start using the commands as if they had built my fork of git
> themselves.

We already have a plugin system, you can drop "git-work" in your
$PATH, what you're talking about is a packaging system, and solving
that problem in a user facing application like Git is IMNSHO a
terrible idea.

Instead you could just make gitwork available somewhere and then
install it as:

    sudo aptitude install git-work

Or whatever incarnation of that your distro or OS provides.

Having our own "gpm" system would mean having to solve all these
issues of distribution, cross-platform & arch compatibility that real
packaging systems already deal with.

If you *really* wanted to go through with this I'd suggest just using
some existing package manager like apt, aliasing it to "gpm", then
configure it to download packages from your own custom repository, and
install them in ~/ somewhere.

You'd still be re-inventing the wheel, but at least minimally so.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]