Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

Hi,

In fact, those ebuilds were done by copiyng old 0.9.2-r1 to the new filename. I made several tests, indicating that ebuilds are working fine. 

Download is going from sourceforge in my test attemps, I think somebody will need to place mysql-python tar's to the gentoo mirrors.

I will attach 2 ebuild files and 2 digests.

Thanks.

Alex

Created an attachment (id=32951) [details]
mysql-python-1.0.0.ebuild

Created an attachment (id=32952) [details]
digest-mysql-python-1.1.1

Created an attachment (id=32953) [details]
digest-mysql-python-1.0.0

Created an attachment (id=32954) [details]
digest-mysql-python-1.1.1

Created an attachment (id=32955) [details]
mysql-python-1.0.0.ebuild

Fixed ebuild by putting unstable flag (~) to all archs

(From update of attachment 32951 [details])
obsolete - it should be unstable

(From update of attachment 32954 [details])
duplicate

Created an attachment (id=32958) [details]
mysql-python-1.1.1.ebuild

Thanks, I added mysql-python-1.0.0 to portage. Btw, next time is good enough
just saying that copying the existing ebuild worked.

Not a big issue, but note that the setup.py has changed in 1.0.0 and newer.
Instead of this:

src_compile() {
        if has_version '>=dev-db/mysql-4.0.10' >& /dev/null ; then
                sed -i 's/thread_safe_library = YES/thread_safe_library = NO/'
setup.py
        fi
        distutils_src_compile
}

you should do this:

src_compile() {
        if has_version '>=dev-db/mysql-4.0.10' >& /dev/null ; then
                export mysqlclient="mysqlclient"
        else
                export mysqlclient="mysqlclient_r"
        fi
        export mysqlversion="$(mysql_config --version)"
        distutils_src_compile
}

None of that thread_safe_library stuff is there anymore. It still works,
though, by virtue of defaulting to using -lmysqlclient. (Please test this; I
wrote the above on the fly.)

Additionally, I'd like to see see 1.1.2 in the Portage tree (masked for
testing, of course) once I release it. 1.1.2 will probably be the last release
before 1.2. I hope to release 1.2 in early July. 1.1/1.2 drops  support for
ancient versions of Python (needs at least 2.3), so it should be faster and
less kludgy/crufty.