BUG: tcl sqlite3 default directory

[afb@…]

Currentl value (/usr/lib/sqlite3) hardcoded for Darwin, provide some more OS alternatives...

[afb@…]

macports-tclsqlite3.patch

[eridius@…]

It seems the entire point of this is to provide a sane default for FreeBSD. I'm not sure we want to do this. We've already decided that MacPorts assumes the user is running on Darwin, and so we can rely on Darwin-specific things, like in this case the location of sqlite3. If you want to override it that's what the --with-tcl-sqlite3 configure switch is for. While it doesn't hurt anything to accept this patch for the short term, I'm worried about this setting a precedent that reverses our previous decision.

Anybody else have an opinion?

[landonf@…]

I agree that --with-tcl-sqlite3 is the better way to override this on a per-OS basis.

I do disagree on the notion of relying on Darwin-specific paths, as hard-coded paths tend to break ... but in this case, it's just a default, so I don't see an issue.

[afb@…]

The only reason for providing defaults was to make "selfupdate" work. As there are no releases since MacPorts 1.4.0, that's the recommended way of installing 1.4.40-42 or the new 1.5/SVN.

[afb@…]

As noted above, the patch doesn't change anything for Mac OS X.

[eridius@…]

ok, if this is necessary for selfupdate to work then I'm ok with us accepting the change.

[jmpp@…]

Milestone Needs developer review deleted

[afb@…]

The last clause works on Linux, it seems.

[afb@…]

Scratch last comment, each Linux distro has it's own install location. :-(

Configure needs to fall back on the internal version, if no system tcl-sqlite3 can be found. With the current script, you end up with:

SQLITE3_DIR=''
SQLITE3_LIBS='-lsqlite3'

Probably rather useless.

[afb@…]

Provided that the sqlite3 libraries are found (but not tcl), it might be possible to use those to build the tcl module with (rather than building the internal/static library)

[afb@…]

macports-tclsqlite3.patch

[afb@…]

Updated patch to fall back on the internal version, don't seem you can build against system libs.