[Solved] live ebuild without SVN or EGIT eclass

[fangorn]

Hi,

I have a set of perl scripts that I want to install with a live-ebuild each. It is just "download the most recent version and copy".

But I am struggling with the source file Manifest that checks (at least) file size and hash.

I know it is just a case of ebuild <package> digest, but I want to spare my users that hassle.

What trick are the EGIT and ESVN? eclasses using that they just download the source, configure and compile?

This is what I have until now:

[Dominique_71]

If your source is a tarball, you wont need the subversion or git.2 eclass. The tarball location must be in SRC_URI, which is not the case now. The ebuild will not be a live ebuild and you have to keyword it.

If your source is some svn repository, you need "inherit subversion" and to use ESVN_REPO_URI instead of SRC_URI. The same apply to git with the git-2 eclass. In both cases, the ebuild will use KEYWORD="".

Also, if you don't need some sections (like src_prepare in your example), you can just remove them from the ebuild. This is for that we have EAPI, to simplify the ebuilds.
_________________
"Confirm You are a robot." - the singularity

[Dominique_71]

And you don't have to create ${S} or to unpack ${SRC_URI}, portage will do this for you, but it must be able to find it. So, you have to put it in SRC_URI. And yes, if your ebuild is not part of an overlay, the user will have to digest it in any case.
_________________
"Confirm You are a robot." - the singularity

[Dominique_71]

For src_install, please use the functions provided by portage: http://devmanual.gentoo.org/function-reference/install-functions/index.html
_________________
"Confirm You are a robot." - the singularity

[fangorn]

Thanks for the reply.

The program is a simple perl script that is hosted uncompressed. The ebuild is just to easily install the dependencies.

As I am actively developing these scripts I don't find the time to update all ebuilds to new versions every few days.

So I want to have ebuilds that do not require to know the script for installation.

That is about it.
_________________
Video Encoding scripts collection | Project page

[Dominique_71]

If you don't want to re-digest the ebuild every time you made a change to some script, the only solution is to use a repository like svn or git.
_________________
"Confirm You are a robot." - the singularity

[steveL]

For the specific situation you outline, I'd do an ebuild that (in src_unpack so you don't get the default) simply uses curl or wget to download the file to "$S", and not have anything in SRC_URI at all.

That way, whenever you emerge it, it simply copies the latest version, and portage makes sure the dependencies are in place. So you only have to digest the ebuild once, when you first put it in the local overlay.

And on subsequent modifications to the ebuild, of course, but not to the underlying script.

It's already keyworded, so user has to unmask it. You don't even need to stick with a 9999 vcs ebuild id: a later version of the ebuild might have updated dependencies, for example (and you might download a matching script version using PV.)

Bear in mind this is not acceptable for general ebuilds: just for your situation, on a private network. (And Gentoo is perfect for that sort of thing.)

[fangorn]

Thanks, that is the solution I was looking for.

I know my ebuilds will never make it into official portage like that, but that is not the intention anyway.

For other OSes I use a different approach. Just the fact that I develop on Gentoo makes me want to
give back to the Community. And it just does not get more easy than

emerge xyz
_________________
Video Encoding scripts collection | Project page

[steveL]

[Dominique_71]

Nice to see it is another solution

[fangorn]

Works like a charm. Thanks Again.

All people interested can find the now working ebuilds on my project page. (See my Signature)
_________________
Video Encoding scripts collection | Project page