Rich Freeman posted on Fri, 22 Feb 2013 10:09:32 -0500 as excerpted:
> On Fri, Feb 22, 2013 at 9:00 AM, Michał Górny <[email protected]> wrote:
>>
>> You can also use git-2 eclass-specific variables to switch the repo.
>> The only difference is that you need to specify the full repo URI
>> rather than just the author.
>
> The full repo URI is actually copy-pastable from github, while breaking
> everything up requires a few steps to configure it all.
>
> I could see some value in being able to switch forks, but that seems
> like a bit of a niche. If you REALLY want to follow another fork you're
> better off creating a new ebuild rather than just overriding the
> environment variable. You can also override the repo URI if it uses the
> git eclass and again that can be copy/pasted.
I I'm involved with pan upstream, I keep a slightly rewritten copy of the
net-nntp/pan-9999 ebuild in my overlay, synced to the one in the tree.
The main difference between it and the tree version is that my version
has:
[[ $EGIT_PROJECT ]] || EGIT_PROJECT="${PN}2"
[[ $EGIT_REPO_URI ]] || EGIT_REPO_URI="git://git.gnome.org/
${EGIT_PROJECT}"
[[ $EGIT_BRANCH ]] || EGIT_BRANCH=master
[[ $EGIT_COMMIT ]] || EGIT_COMMIT=$EGIT_BRANCH
That allows me to keep an /etc/portage/env/net-nntp/pan file where I can
set those as I wish, as well as keep (normally commented) vars such as
EGIT_COMMIT, EGIT_OFFLINE, etc.
=:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
