Mailinglist Archive: opensuse-bugs (4060 mails)

< Previous Next >
[Bug 662186] New: [SMBTA] smbtad to deliver sqlite3 and link statically
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 4 Jan 2011 06:42:54 +0000
  • Message-id: <>

Summary: [SMBTA] smbtad to deliver sqlite3 and link statically
Classification: openSUSE
Product: openSUSE 11.3
Version: Final
Platform: Other
OS/Version: Other
Severity: Normal
Priority: P5 - None
Component: Samba
AssignedTo: hhetter@xxxxxxxxxx
ReportedBy: hhetter@xxxxxxxxxx
QAContact: samba-maintainers@xxxxxxx
CC: bgeuken@xxxxxxxxxx, mhaefner@xxxxxxxxxx,
Blocks: 656695
Found By: ---
Blocker: ---

I open this bug after a long thought about it. In general I don't like the idea
of delivering self contained libraries with the packages, as the packager has
to care for the healthiness of the contained code. And in the end, shared
libraries are there for a reason.

Due to my effort to bring smbtad to Tumbleweed, this discussion came up again,
since I was suggested to statically link smtbad against the sqlite version it
requires instead of upping the sqlite version in tumbleweed. This doesn't make
sense to me in the light of the idea of Tumbleweed, but the static linking
suggestion is something to consider for SMBTA itself.

- we had very conservative platforms to run smbtad in the past (non Linux),
where it was a PITA to have to install sqlite to make smbtad to build
- due to the embedded nature of sqlite, it looks like all larger oss projects
are just including their own version and some don't even consider to look at
shared sqlite objects.
- we can make the static build/linking for smbtad completely optional

As said, I generally don't like the idea, but considering the practical
advantages telling me a different story currently. Also, this can be made
completely optional.

So I propose to include a sqlite build in smbtad 1.2.2

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >