Alin Năstac kirjoitti:
Petteri Räty wrote:
Alin Năstac kirjoitti:
Petteri Räty wrote:
Benedikt Morbach kirjoitti:
In my humble opinion it would be nice to have a greater degree of
control by separating this into two useflags, sqlite2 and sqlite3,
just like e.g. qt3 and qt4
Probably. Even
If a program supports both then go with sqlite3. The things is that
there are sqlite2 only things left. I don't have much interest in sqlite2.
For anyone interested: I dropped sqlite2 from the new qt-4.4 currently masked in
portage. I also made it so that the sqlite flag just turns on
Alin Năstac kirjoitti:
Petteri Räty wrote:
Benedikt Morbach kirjoitti:
In my humble opinion it would be nice to have a greater degree of
control by separating this into two useflags, sqlite2 and sqlite3,
just like e.g. qt3 and qt4
Probably. Even better would be to get rid of sqlite2 but
Petteri Räty wrote:
Alin Năstac kirjoitti:
Petteri Räty wrote:
Benedikt Morbach kirjoitti:
In my humble opinion it would be nice to have a greater degree of
control by separating this into two useflags, sqlite2 and sqlite3,
just like e.g. qt3 and qt4
Probably. Even better would be to get
Benedikt Morbach kirjoitti:
In my humble opinion it would be nice to have a greater degree of
control by separating this into two useflags, sqlite2 and sqlite3,
just like e.g. qt3 and qt4
Probably. Even better would be to get rid of sqlite2 but that probably
doesn't happen any time soon.
Petteri Räty wrote:
Benedikt Morbach kirjoitti:
In my humble opinion it would be nice to have a greater degree of
control by separating this into two useflags, sqlite2 and sqlite3,
just like e.g. qt3 and qt4
Probably. Even better would be to get rid of sqlite2 but that probably
doesn't