Writing an ebuild from a .deb [Solved]

Message

aCOSwt · Post by **aCOSwt** » Sun Mar 25, 2012 8:04 am

Thanks to this : http://devmanual.gentoo.org/ebuild-writ ... index.html
It has been a piece of cake to write an ebuild for some rpm packed package.

Is there something equivalent concerning a .deb or a quick & dirty way to write an ebuild for a .deb packed package ?
(The package mostly consists in python scripts, some depending on the python-tk tkinter library).

PaulBredbury · Post by **PaulBredbury** » Sun Mar 25, 2012 8:26 am

Add a space before the comma, after the URL, or it makes the URL invalid

What you're asking for, doesn't really exist. You might as well ask, where is the decent English-to-Chinese translation software

Different *styles*, and it's not easy to explain a style to a computer.

aCOSwt · Post by **aCOSwt** » Sun Mar 25, 2012 8:57 am

PaulBredbury wrote:What you're asking for, doesn't really exist. You might as well ask, where is the decent English-to-Chinese translation software

The package is actually a @#ç to 12

translation software !

So... I believe this is coherent...

OK, I can understand what you mean. As it had been rather simple starting with a .rpm thanks to the devmanual and I had seen a todo from Vapier with debian sources on the following pages... I was just... hoping !

Thank you.

i92guboj · Post by **i92guboj** » Sun Mar 25, 2012 9:08 am

There's this that I saw the other day when searching for some other -unrelated- thing.

http://code.google.com/p/cj-overlay/sou ... b001ec9b2f

But I haven't tested it myself so I can't comment on it.

aCOSwt · Post by **aCOSwt** » Sun Mar 25, 2012 9:32 am

A convenience class for extracting deb packages ! That does look like what I should start with.

Thank you, i92guboj, I am going to dig into this more closely.

PaulBredbury · Post by **PaulBredbury** » Sun Mar 25, 2012 9:45 am

You're doing this the wrong way.

Use the upstream source (rather than the debianized source, recognizable by their love of underscores in filenames), then just apply the patches from the patches/ dir, from the Debian patch file. 99% of the rest can be ignored.

It's easy.

There's absolutely no need for ebuild "helpers", when you have to figure out what the heck the helpers are doing. Is this process not simple enough already? I've done it loads of times in Lunar - a favourite of mine is to use Ubuntu's xorg-server 1.10.4, which is rock-solid.

aCOSwt · Post by **aCOSwt** » Sun Mar 25, 2012 4:41 pm

PaulBredbury wrote:You're doing this the wrong way.

Well, to be honest, I had no way at all when starting this thread...

PaulBredbury wrote:Use the upstream source

The problem is that upstream source is, AFAIK available only in a MS self installer and I know nothing about this stuff and my msexpand does not either.

PaulBredbury wrote:(rather than the debianized source, recognizable by their love of underscores in filenames)

Certainly a conflict of generation... I do not mind... I belong to the generation which was not allowed to fill filenames with fancy characters and I still cannot stand filenames with spaces.

PaulBredbury wrote:There's absolutely no need for ebuild "helpers"

You are certainly right. And I make no doubt that when you become experienced in any matter, you smile when considering what helpers are doing.
But, you know... from my standpoint, helpers are just great for highlighting things that I would have forgotten even if obvious and basic...

PaulBredbury · Post by **PaulBredbury** » Sun Mar 25, 2012 4:51 pm

aCOSwt wrote:MS self installer

Ah. There's a case where helpers are actually *good*, e.g. Gentoo's unpack_makeself function (IIRC the name).

aCOSwt · Post by **aCOSwt** » Mon Mar 26, 2012 1:28 pm

OK ! Done ! Thank you both for helping.

Using unpack_makeself lead me into further complications, well, I mean uselessly complicating the ebuild.

So I followed i92guboj track, found in the unpacker eclass the unpack_deb helper and then simply followed Vapier's way of working... as written in the Gentoo Development Guide... ("you could just extract it to /")

For those who would be interested in the basic principle :

Code: Select all

...
inherit ... unpacker ...
...
src_unpack(){
        unpack_deb ${A}
...
}
...
src_install(){
...
        cp -R "${WORKDIR}/usr" "${D}" || die "install failed!"
...
}
...

Just too easy !