From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from vestibule.its.caltech.edu (vestibule.its.caltech.edu [131.215.48.17]) by chiba.3jane.net (Postfix) with ESMTP id 1B4E5ABD7F for ; Thu, 18 Apr 2002 01:59:18 -0500 (CDT) Received: from groug.home.net (PPP-36-148.caltech.edu [131.215.36.148]) by vestibule.its.caltech.edu (8.9.3/8.9.3) with ESMTP id AAA07277 for ; Thu, 18 Apr 2002 00:00:47 -0700 (PDT) Content-Type: text/plain; charset="windows-1251" From: George Shapovalov To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] ebuild question Date: Wed, 17 Apr 2002 23:59:12 -0700 X-Mailer: KMail [version 1.4] References: <1019110387.12142.46.camel@seahorse> In-Reply-To: <1019110387.12142.46.camel@seahorse> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200204172359.12889.georges@its.caltech.edu> Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: f668e422-0195-4b4c-aa90-33067dc50eea X-Archives-Hash: 00c4caf73cb75bba054de91db80705cd Hi It is hard to answer many of these questions without seeing the package a= nd=20 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 th= e=20 easiest way to go around here. You also would probably want to set your=20 ${S}=3D${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=20 going to prepare the list of all vars portage generates when it parses eb= uild=20 and link to it from the existing ebuild composition howto. I would apprec= iate=20 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=20 wingide-1.1.3-1.ebuild unpack and then go to=20 /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 id= ea=20 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 roo= t > 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=20 > 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 extract= ed? 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= =2E > 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 i= t > for me? I think you do. I am not totally clear on what are you trying to achieve = here=20 though. Besides this is you who tells ebuild what to do and if the dir wa= s=20 not created by the package installation scripts ebuild will not know to=20 create it on itself. BTW, is this a prebuilt package or can it be compiled (the last one is al= ways=20 preferable). Is this a WingIDE by any chance? Is this a (time-limited) de= mo=20 version? I think the users are required to register on the site when=20 downloading the product (in order to get the license). You will most like= ly=20 have to do something about it (I am not really sure on the status of this= =20 package). At present you can ask users to download the package themselves= and=20 put it under /usr/portage/distfiles before proceeding. It may change in=20 (probably already near) future when licensing stuff is handled in portage= =2E George