Re: [gentoo-dev] SRC_URI="gogdownloader://..."

[James Le Cuirot]

On Sun, 2 Oct 2016 22:06:19 -0400
Ian Stakenvicius <axs@g.o> wrote:

> On 02/10/16 04:59 PM, James Le Cuirot wrote:
> > On Sun, 2 Oct 2016 21:48:04 +0100
> > James Le Cuirot <chewi@g.o> wrote:
> >
> >> SRC_URI="gogdownloader://tomb_raider_1/en1installer1 ->
> >> setup_tomb_raider_${PV}.exe" IUSE="gogdownloader"
> >> RESTRICT="!gogdownloader? ( fetch ) mirror"
> >> DEPEND="games-util/lgogdownloader"
> >
> > Probably goes without saying but that should have been:
> > DEPEND="gogdownloader? ( games-util/lgogdownloader )"
> >
>
> So I think the idea of supporting this is great, but I think the best
> way to go about it is to support it in the same manner that the VCS
> eclasses do -- that is, DONT use SRC_URI but instead use GOG_URI , and
> have the gog eclass within src_unpack handle the actual fetching.
>
> If in a future EAPI we get src_fetch() and the ability to specify
> custom fetching, then this can be improved, but for now I'd say do it
> the same as the VCS eclasses do.

src_fetch would be nice for VCS but I think it's overkill here as what
we have already works fine. If Portage were as flexible with its
configuration as Paludis, there would be no issue, save for doing away
with the static list of protocols in the PMS.

The simplest solution I can see would be to make make.globals a
directory and then packages like lgogdownloader could just drop files
in there. This could have other uses too. Can't think of any right now
though. ;)

Instead of dictating the list of supported protocols, PMS could then
say something to the effect of:

"As well as supporting the http://, https://, ftp:// protocols out of
the box, the package manager must be sufficiently configurable to allow
packages to extend this list by installing additional files."

Different files would need to be installed to support both Portage
(plus pkgcore) and Paludis but I could live with that. Otherwise
Portage would probably need to implement fetchers the same way that
Paludis does. The end result would be nice but could we seamlessly
migrate existing user configuration? How many users actually change
FETCHCOMMAND?

http://paludis.exherbo.org/configuration/fetchers.html

I understand that a new EAPI would still be required as there is
otherwise no guarantee that the user will have a version of Portage
with this fix, short of depending on sys-apps/portage, which is bad! In
the meantime, I'll have to make do with src_unpack. I'll also file a
bug so we can further discuss which avenue to take.

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer