Re: bitpim binary modules breaks Gentoo QA policies

> it doesnt support sony ericsson phones does it ?  

Nope.

> ive got a T226 that supports like OBEX or something 

OBEX is actually a standard, although you'll find quirks
with each model.  If the phone supports SyncML (higher
numbered models do) then you are in luck:

http://multisync.sourceforge.net/news.php

All it takes to get your phone supported in BitPim is someone with
the phone and some time.

> odd ... downloading the apsw source zip (apsw-3.2.7-r1.zip) and proceeding to 
> run `python setup.py build` produces a proper apsw.so for me ... you say 
> you're building this on the Redhat 9 box ?  wonder if the distutils that you 
> have installed on there are outdated and dont build proper shared objects 
> with -fPIC ...

That would likely be the case.
 
> fun !  i'll have to ponder hard on this one ... is there no package which 
> provides the `bmp2avi` util ?

That is in the bitpim code.  
http://svn.sf.net/viewcvs.cgi/bitpim/trunk/bitpim/src/native/av/bmp2avi/

It just uses g++ -o foo foo.o (on Redhat 9).
 
>> My other suggestion was a seperate package (eg gentoo-rpm)
> 
> an interesting concept ... and i doubt the basic implementation would present 
> too much trouble ... simply unpacking an rpm, inserting relevant portage 
> information, and not worrying about crap like dependencies ...

The existing BitPim ebuild does exactly that!  It inherits rpm.eclass
which basically unpacks the rpm into the source directory (using
rpm2cpio).  The trick is to then get the files into the installed
packages list.  Have a look at app-portage/g-cpan
What it does is creates a new ebuild on the fly.  It is overengineered
for our purposes since it also creates dependent CPAN module ebuilds
and a whole bunch of other crud.  If someone wants to write a
tool like this then I am prepared to help (primarily with testing).

Rant mode on:  For some bizarre reason, none of the various Linux
packaging systems provide a binary that can be run that lets
you add a file to the installed files database.  This makes it
impossible for post install scripts to adjust to the installed
system.  For example you can't do this:

  if .... some random condition ...
  then
       add-to-filedatabase MyPackageName /etc/foo.conf
  else
       add-to-filedatabase MyPackageName /var/etc/foo.conf
  fi

The SVR4 packaging system has had this for years.  The command name
is installf:

  http://docs.sun.com/app/docs/doc/806-0625/6j9vfiloh?a=view

If something like this existed, it would make the tool we
are talking about trivial.  Expand the rpm and then run
installf with the relevant files.  Instead you have to go
through hoops making dummy ebuilds.  

RPM doesn't this kind of command either.  It would have been a
great help when I used to supply man pages with earlier software
I did.  No two systems could decide if man pages were gzipped or
bzipped, or where they lived.  Consequently the postinstall 
could easily have compressed them the right way and put them in
the right directory for that system.

Here is another good example usage:

  http://www.redhat.com/archives/rpm-list/2001-November/msg00308.html

Roger


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642