Re: Help packaging the latest pidgin.

2008/1/30, Neil Munro <[email protected]>:
> Once i reached the point of trying to get my head around binreloc I got
> lost. I know why it's required and what it does I'm just not quite sure HOW
> to do it. Especially considering this application is not mine and I don't
> know the code. Can someone help me package the latest pidgin and walk me
> through all the things I need to do. Hopefully after packaging a few times
> I'll get my head around it and know what to do in future.

Pidgin was once upon a time packaged with autopackage (back when it
was called Gaim) so there shouldn't be too hard to make that work
again. (Tim, are you still on this list?)

On the other hand, pidgin is also quite a large project, which means
you'll probably have to get your hands dirty while doing it.

There are two ways to use binreloc.
1) The "normal" way: This involves changing the code to not rely on
hard coded paths. Basically find all locations in the code where it
has hard coded strings for e.g. datafiles and replace them with their
corresponding binreloc API function call.
2) The "new-not-so-tested" way: By using some file descriptor black
magic, you may be able to get pidgin completely "binreloced" without
touching the code. See
http://trac.autopackage.org/browser/binreloc/trunk/fdbr.c . Also see
this thread: http://thread.gmane.org/gmane.comp.autopackage.devel/5274/focus=5278

-Isak

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]