Re: [gentoo-dev] ebuild question

[George Shapovalov]

Hi

It is hard to answer many of these questions without seeing the package and 
ebuild. However I'll try.

On Wednesday 17 April 2002 23:13, Avi Schwartz wrote:
> I am trying to create an ebuild for wingide.  I have couple of problems
> I trying to solve here:
>
> 1. The name of the archive is wingide-1.1.3-1.tar.gz.  I tried to call
> the ebuild file wingide-1.1.3-1.ebuild but ebuild doesn't like it since
> it thinks there are two version numbers.  So I changed the name to
> wingide-1.1.3-r1.ebuild and I am sticking the -1 in the code:
[skipped]
> Is this an acceptable practice? The problem with this is that if they
> come out with a -2 version, it will not be enough to rename the ebuild
> file (although the bug fix files are breaking this anyway).
At least this is what you can find in some ebuilds. And it seems to be the 
easiest way to go around here. You also would probably want to set your 
${S}=${WORKDIR}/${P}-1.

>
> BTW, PV and ${D} are not documented in the developers HOWTO.  What else
> is missing?
I hope I finally will get some time to update this part of instructions. I was 
going to prepare the list of all vars portage generates when it parses ebuild 
and link to it from the existing ebuild composition howto. I would appreciate 
suggestion on what else should be covered.

>
> 2. Wingide comes with its own installation program which can be
> controlled through the command line.  When its archive is expanded, it
> creates a wingide-1.1.3-1 directory in which there is the installation
> program and the program files.  Ho do I point to the installation
> program?  I tried the following ${WORKDIR}/${P}-1/wing-install.py, is
> this correct?
Does it work? In order to check this you can issue ebuild 
wingide-1.1.3-1.ebuild unpack and then go to 
/var/tmp/portage/wingide-1.1.3-1/work and see what goes where.

>
> 3. The parameters it expects are the installation directory and binary
> directory:
>
>     ${WORKDIR}/${P}-1/wing-install.py  \
>         --winghome ${D}/usr/lib/wingide \
>         --bin-dir ${D}/usr/bin
>
> again, does this make sense?
Is this analog of configure script or of make install?
You do not want anything that gets compiled or somehow setup to get an idea 
that it lives under ${D}. However you do want it to be installed under ${D}.

> 5. The last 3 files are archives that have to be extracted over the root
> installation directory which will be ${D}/usr/lib/wingide.  Again, how
> does one achieve this?
what about this?
cd ${D}/usr/lib/wingide
tar xzpf file 

> 6.  The compile stage extracts all 4 files while I really want only the
> main file to be extracted since the other 3 need to be extracted over
> the installed file.  Is there a way to control this?  I tried to put my
> own code in src_compile(), but ebuild goes ahead and extracts the
> archives before executing my code.
Are you talking about unpack or compile stage? When the files are extracted?
You might need to provide src_unpack function to do custom stuff.

> 7. When the wingide archive is extracted, besides the installation
> program there is another tar file extracted which containsall the files.
> Another possibility for the installation of the main wingide archive is
> to just extract this archive into ${D}/usr/lib.  The question is, do I
> have to create ${D}/usr/lib if it doesn't exist yet or will ebuild do it
> for me?
I think you do. I am not totally clear on what are you trying to achieve here 
though. Besides this is you who tells ebuild what to do and if the dir was 
not created  by the package installation scripts ebuild will not know to 
create it on itself.
BTW, is this a prebuilt package or can it be compiled (the last one is always 
preferable). Is this a WingIDE by any chance? Is this a (time-limited) demo 
version? I think the users are required to register on the site when 
downloading the product (in order to get the license). You will most likely 
have to do something about it (I am not really sure on the status of this 
package). At present you can ask users to download the package themselves and 
put it under /usr/portage/distfiles before proceeding. It may change in 
(probably already near) future when licensing stuff is handled in portage.

George