Bugzilla Bug 119498

ebuild for latest stable release.  note i added a 'swig' local use flag for
rebuilding the swig-based language bindings.   i also included the language
binding examples in the docs.   ebuild attachment follows.

Created an attachment (id=77486) [details]
obexftp-0.18.ebuild new ebuild

a diff -Naur to the existing beta ebuild follows as another attachment.

Created an attachment (id=77487) [details]
obexftp-0.18.ebuild.patch

Created an attachment (id=77488) [details]
obexftp-0.18.ebuild

Created an attachment (id=77489) [details]
obexftp-0.18.ebuild.patch

*** Bug 119547 has been marked as a duplicate of this bug. ***

Created an attachment (id=77550) [details]
obexftp-0.18.ebuild

cleaned-up so the deps represent minimum stable versions as they exist in
portage.

Created an attachment (id=77551) [details]
obexftp-0.18.ebuild.patch

diff -Naur patch against existing portage ebuild.

Any particular reason for useflagging swig? Why rebuild language bindings when
this operation is better done by upstream (before package release, of course)?

No compelling reason really.  Christian Z. added --enable-swig (default=no] for
those who wish to rebuild the swig language stubs.   His pre-packaged ones
certainly work on gentoo (at least they do here on x86).  You could toss swig
and even the debug stuff I added if you were so inclined.   Perhaps Christian
could chime in if he felt it were genuinely important.

obexftp is being developed on x86 gentoo, that makes --enable-swig most likely
redundant. On the other hand isn't gentoo about building everything from source
after all? So if a user has swig installed, make it spin ;)
I'm more worried about the automatic en-/disable of the language bindings.
Works for me, but perl, python and tcl are fully installed here anyway.

It is true we build our packages from the source, but this looks like
over-configuration to me.

From what I understand, swig is a way to translate calls to your library in
other languages (especially the scripting ones). Since we do not change the
source of the package, I very much doubt it would make a difference in pl,ty or
tcl files.
The fact that no other gentoo package has useflags regarding swig seems to
confirm my opinion. If I'm wrong, please let me know.

Also the doc flag also seems a bit much. Normally it is used for extra
documentation that requires significant amount of resources to either create or
store. I'm thinking about dropping it and just install those file
unconditionally.

The debug flag on the other hand, is useful for obex developers so I will leave
it as is.

Right no need to introduce a useflag (swig) that nobody can make sense of and
that can hardly be useful.
You can drop the doc flag safely. The doc dir used to contain lots of generated
files but is mostly empty now (we moved everything to some wiki).

Christian, it's probably best to keep the swig stuff disabled by default in
your configure.in (as it is now).  Don't use 'auto' detection for swig, as you
do with some of the other flags.  This will prevent potential meta-packaging
(ebuilds and such) problems down the road.   Phil

By the way, I posted an ebuild for your obexftp fuse wrapper, obexfs-0.7, here
on bugzilla as Bug 119500.   Phil

Alin, if you want to take over obexftp maintainership, go ahead - my free time
has shrunk recently, and I have barely time to maintain packages I actually
use. Obexftp deserves better.

version bumped.

I don't really use this package, so I cannot become its maintainer.
You could delete your maintainer entry from metadata.xml. mobile-phone herd
will take care of it.