After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596616 - $libdir/seed/*.so might conflict in the future
$libdir/seed/*.so might conflict in the future
Status: RESOLVED DUPLICATE of bug 639896
Product: seed
Classification: Bindings
Component: libseed
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: seed-maint
Depends on:
Blocks:
 
 
Reported: 2009-09-28 15:16 UTC by Dominique Leuenberger
Modified: 2011-02-17 05:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Leuenberger 2009-09-28 15:16:09 UTC 
Currently, seed installs files into $libdir/seed/

If anywhen in the future a new version of libseed.so.1.0.0 (for example) is coming out, those two libraries would not be able to installed in parallel, as $libdir/seed would conflict between them and most likely cause random errors / crashes.

Suggestion to use versioned directory for any relevant directory used by a library.

for example
$libdir/seed0 to show it goes together with libseed.so.0 and similiar directories in the future.
Comment 1 Tim Horton 2009-12-16 04:19:35 UTC 
I'm not totally aware of how things work in the long term; is this something that it's appropriate to change at this point in time?
Comment 2 Dominique Leuenberger 2009-12-16 09:10:18 UTC 
I was always a believer that it's easier to fix a problem before it is a real one :)

The fix could really be as easy as using $libdir/seed0, which refers to libseed.so.0. More complex would be (but not wrong neither) $libdir/seed-$version

As said, the issue will be at hand when two libseed.so.* versions need to be installable in parallel (not all apps being rebuilt against the new ABI/API) and then they would mess up with various files in one common folder as set up now.
Comment 3 Frederic Crozat 2011-02-02 16:21:08 UTC 
I'd suggest duplicating this bug with bug 639896 where I fixed this issue
Comment 4 Alan Knowles 2011-02-17 05:28:04 UTC 
This should be fixed thanks to Frederic's patch - if not please re-open.

*** This bug has been marked as a duplicate of bug 639896 ***