| 1 |
Alin Năstac kirjoitti: |
| 2 |
> Mike Frysinger wrote: |
| 3 |
>> how about 'sqlite' means you want sqlite irregardless of version ... then |
| 4 |
>> sqlite-2 either gets punted from apr-util or it gets a local USE |
| 5 |
>> flag 'sqlite-old' for older cruft |
| 6 |
>> |
| 7 |
> Wouldn't be better to determine what version of sqlite should be used |
| 8 |
> based on the version of sqlite currently installed on the system? |
| 9 |
> Something like: |
| 10 |
> sqlite_atom=$(best_version dev-db/sqlite) |
| 11 |
> sqlite_major_version=${sqlite_atom#*/*-} #reduce it to $PV-$PR |
| 12 |
> sqlite_major_version=${sqlite_major_version%%.*} # major version |
| 13 |
> |
| 14 |
> ... ebuild stuff... |
| 15 |
> econf \ |
| 16 |
> $(use_enable sqlite sqlite${sqlite_major_version}) |
| 17 |
> |
| 18 |
> Better yet, why not make an sqlite.eclass that would contain at least |
| 19 |
> get_sqlite_major_version()? |
| 20 |
> |
| 21 |
|
| 22 |
No. The produced binaries can't depend on the build system like this. |
| 23 |
Breaks binary packages etc. |
| 24 |
|
| 25 |
Regards, |
| 26 |
Petteri |
Archives