On Sat, 2019-08-17 at 09:42 -0400, Michael Orlitzky wrote:
> On 8/17/19 4:54 AM, Michał Górny wrote:
> > On Sat, 2019-08-17 at 10:52 +0200, Ulrich Mueller wrote:
> > > Shouldn't there be a blocker against dev-vcs/gitolite{,-gentoo}
> > > (and vice versa)? These packages cannot be installed at the same time,
> > > and I guess that a direct blocker would result in a friendlier error
> > > message than REQUIRED_USE magic in acct-user/git.
> > >
> >
> > You're probably right. I'll update the patches to add mutual blockers
> > everywhere.
> >
>
> I discovered on the pull request that "git" is just the name that the
> upstream examples use, but isn't required for either gitolite or gitea:
>
> * https://docs.gitea.io/en-us/install-from-binary/
>
> * https://gitolite.com/gitolite/concepts#the-hosting-user
>
> For example, on Fedora and Debian, gitolite uses a "gitolite" user. We
> should also be able to use "gitea" for gitea, meaning that the two
> packages don't have to block each other, and that they don't have to
> fight over the same username.
>
> I realize we'd have to tell people how to rename the account to support
> upgrades -- but is there some other reason to keep the shared "git" name?The argument I've been told is that users expect 'git@...' to work as remote URI on their boxes. They don't want users to bind the URI to specific implementation. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
