Re: bitpim binary modules breaks Gentoo QA policies

Roger Binns wrote:

> ...
>
> The correct fix and the Gentoo philosophy is that this should
> be run/built from "source".  However there are several problems.
> Firstly the Gentoo release procedures cannot keep up.  There
> is a new BitPim release every three weeks (it used to be every two).
> Consequently things will be long obselete by the time ~x86 is
> removed.

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

>
> Given these problems with portage, someone started making
> ebuilds that just grab the rpm and untar it.  Even then they haven't
> keep up with the release schedule.
>
> Unless someone at Gentoo is prepared to own the effort and
> put proper time into this, then I am not going to do anything
> differently. 
> If someone will do that, then they need to do the following.
> I will give them full assistance, and also make some code
> changes that will help.  Doing this will also get you
> BitPim working on all architectures (there are no CPU or
> 32/64 bit dependencies)


who says that every release should be immediately available in all
distros? does Debian or Redhat include the update whenever you release a
new versions?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEB+7iRZBYwhawvi4RAmz2AJ9NS18U4NZC5PlCRiqFpkJRVr7bXACgl+tZ
yivCeB/Do4yePRPxBwjbBs8=
=71VR
-----END PGP SIGNATURE-----