Trying to be clever, I wanted to modify the Trac info file such that
it would not require pysqlite2-py26. (Python 2.5 and later come with
the sqlite3 library, which is compatible with pysqlite2.)
Here's the crazy dependency line:
Depends: <<
...
(%type_raw[python] = 2.6) python26 |
(%type_raw[python] = 2.5) python25 |
(%type_raw[python] = 2.4) pysqlite2-py%type_pkg[python] (>=
2.4.1-1) |
mysql-python-py%type_pkg[python] | psycopg2-py%type_pkg[python],
...
The basic idea is that you can use either SQLite, MySQL, or Postgres
as your database backend.
However, the above expands as follows (in -py26, -py25 and -py24
variants):
depends: ..., python26 | mysql-python-py26 | psycopg2-py26, ...
depends: ..., pysqlite2-py25 (>= 2.4.1-1) | mysql-python-py25 |
psycopg2-py25, ...
depends: ..., pysqlite2-py24 (>= 2.4.1-1) | mysql-python-py24 |
psycopg2-py24, ...
I'm curious as to why the -py25 variant depends on pysqlite2-py25
instead of python25.
Is there an order of operations that I should be aware of with variants?
thanks,
--
Charles Lepple
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
