Re: bitpim binary modules breaks Gentoo QA policies

> that would be the preferred way, but since you do not provide the source
> tarball in your releases, it cannot be done.

The tree is tagged - do a check out on the tag.  For example the most
recent release was tagged BITPIM_0_8_08.  We haven't done the first
release from the new Subversion repository yet but will do soon
at which point there will be a tag namespace there.

> please add the  source tarball to your future releases.

No.  The SourceForge file release process is far too annoying.
As I mentioned in the previous mail, that is why I don't
have builds for other versions of Linux distros.

If you are prepared to go through the SourceForge upload process with 
each release I'll happily email you the tarball each time to 
do so.

> who says that every release should be immediately available in 
> all distros? 

I do and the users do.  BitPim changes for the better noticeably
with each release.  That is a major part of the reason why the
releases are so frequent.  We update a lot of the phone model 
support as well as features/functionality common to all phones.

Telling users there is a new version (ie removing ~x86) only
to have them find out it is 3 months old and the current release
works with their phone better doesn't help anyone.

ie there is something in place now that works well now, and is
always up to date.  Proposing to make that significantly worse
isn't that interesting to me.

> Does Debian or Redhat include the update whenever you release 
> a new versions?

They don't supply BitPim.  The users grab it from the BitPim
web site.

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