Re: [gentoo-portage-dev] Custom eclass question

[John Myers]

DISCLAIMER: I am not a dev.

On Sunday 09 October 2005 16:52, Mikey wrote:
> I recently posted a question in the Portage & Programming forum and was
> told that this mailing list might be the place to go.  Any help would be
> greatly appreciated.
>
> I have a custom in-house web based source code/packaging repository system
> that I need to integrate into ebuilds. It is kind of like a funky cvs
> system.  Source code and packages are all viewed or downloaded via a
> browser.
>
> For example, to retrieve a gzipped tarball of a package named "mypackage"
> from the repository looks like:
>
> http://codeserver.wherever.net/pman/package_ids.php?action=package&id=10105
Is the id->name mapping 1:1? Since this is an in-house app, can you write a 
script which has nice names, perhaps using $_SERVER['PATH_INFO'], i.e.
	http://codeserver.wherever.net/pman/package_dl.php/mypackage.tar.gz
? In one of my web apps, I use PATH_INFO with Apache's Multiviews to make 
clear, permanent, search-engine-friendly paths to my c ontent pages, 
	http://example.com/content/<name>/pages/<page number>
which is served by a file named content.php in the site's root, using files 
outside the DocumentRoot that hold the actual content.

>
> On any standard browser (konqueror, IE, firefox) this would retrieve a file
> named "mypackage.tar.gz".
wget doesn't support that.

> Here is where my problem starts, and why I believe a custom eclass might be
> my best route.
>
> The utility that fetches packages via emerge mangles the resulting file
> name, as well as wget (does emerge use wget?). When fetching the above url,
> emerge or wget saves the file as "package_ids.php?action=package&id=10105".
> This of course throws a wrench into my use of custom ebuilds :)
emerge uses wget via $FETCHCOMMAND, which doesn't include a place for -O

> My problem is that I cannot seem to locate where any package fetching
> routines are in any of the existing eclasses to use as a template.
I think that's because they're not there. IIRC, fetching is more internal than 
that.
> Another
> thing I am curious about, will custom eclasses in PORTDIR_OVERLAY work
> correctly (assuming they are written correctly).
Partly. From what I've read, I think you have to touch all the ebuilds that 
inherit the eclass every time you change the eclass.

Other people have run into this problem before, and recently. You might want 
to check the archives of both this list and gentoo-dev.

-- electronerd