HOWTO write ebuild for non-conformant filename [SOLVED]

[binro]

I want to install protoeditor which is not in portage. To keep thinks kosher I thought I would write my own ebuild in my overlay. However the download file name is

Code: Select all

protoeditor-1.1beta3

and an ebuild of that name is not allowed by portage. I can change the ebuild name to

Code: Select all

protoeditor-1.1_beta3.ebuild

but then the download fails. If I download the file first and change its name, the compile stage fails because the unpacked source directory still has the old name. How do I avoid having to download the tarball first, unpacking it, renaming it and packing it up again?

TIA

[sageman]

What's the ebuild look like? Can you post it here?

[binro]

protoeditor is a standard KDE app so I just copied another one:

Code: Select all

inherit kde

DESCRIPTION="Python debug editor"
HOMEPAGE="https://sourceforge.net/project/showfiles.php?group_id=129439"
SRC_URI="http://jaist.dl.sourceforge.net/sourceforge/protoeditor/${P}.tar.gz"
LICENSE="GPL-2"

SLOT="0"
KEYWORDS="x86"
IUSE=""

need-kde 3

[sternklang]

Take a look at the Variables page of the Gentoo Development Guide, specifically the last section on the page, "Version Formatting Issues" for an explanation of how to handle this. The devguide is an excellent resource if you want to know the correct way to write an ebuild.

[lnxz]

Code: Select all

MY_P="protoeditor-1.1beta3"
S="${WORKDIR}/${MY_P}"
SRC_URI="http://jaist.dl.sourceforge.net/sourceforge/protoeditor/${MY_P}.tar.gz

not very pretty, but it might be a starting point.

[PaulBredbury]

Should be:

Code: Select all

MY_P=${P/_beta/beta}
...
HOMEPAGE="http://sourceforge.net/project/showfiles.php?group_id=129439"
SRC_URI="mirror://sourceforge/${PN}/${MY_P}.tar.gz"
...
S="${WORKDIR}/${MY_P}"

[binro]

Thanks guys, that's what I needed to know!

[binro]

Ok, the ebuild now finds and compiles the right source but at the install stage I get this:

• Making install in libs
  make[2]: Entering directory `/var/tmp/portage/protoeditor-1.1_beta3/work/protoeditor-1.1beta3/data/libs'
  mkdir -p /usr/share/apps/protoeditor/libs/perl/
  tar xfz ../../data/libs/perl_dbgp.tar.gz -C /usr/share/apps/protoeditor/libs/perl/
  ACCESS DENIED open_wr: /usr/share/apps/protoeditor/libs/perl/DB/IO/Scalar.pm
  tar: DB/IO/Scalar.pm: Cannot open: Permission denied
  ACCESS DENIED open_wr: /usr/share/apps/protoeditor/libs/perl/DB/IO/Stringy.pm
  tar: DB/IO/Stringy.pm: Cannot open: Permission denied
  ACCESS DENIED open_wr: /usr/share/apps/protoeditor/libs/perl/DB/IO/Wrap.pm

Since I am running as root, has emerge su'ed to some other userid? I have never seen this problem before in two years of Gentooing! If I cd to the work directory and "make install" the installation completes correctly. Other packages emerge as usual.

[sternklang]

Portage builds packages within a sandbox, then during the install phase copies the files from the sandbox to the live filesystem. These ACCESS DENIED errors mean the install script or makefile is trying to write outside the sandbox.

Take a look at the makefile and find the places where it's doing this. Then, modify the makefile to put "${D}" in front of the destination paths so when "make install" is run the files will be copied to the sandbox. You can either use sed to modify the makefile from the ebuild or create a modified makefile, diff the makefile to create a patch, and use epatch in the ebuild to apply the patch to the makefile. In either case, you would change the makefile in the src_unpack function. Take a look at the development guide for more details.

[binro]

Sternklang, thanks for the pointers. Basically, what you are saying is that the package's makefiles are badly constructed, in which case I shall not worry to much. However, I shall give massaging the makefiles with sed a go...