Bug 12443 - XDG_DATA_DIRS conflict between preinstalled and hand-built stap
Summary: XDG_DATA_DIRS conflict between preinstalled and hand-built stap
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-26 13:54 UTC by Frank Ch. Eigler
Modified: 2012-12-20 15:31 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Ch. Eigler 2011-01-26 13:54:07 UTC 
If one builds a version of systemtap by hand, but one also has a pre-installed
version to which $XDG_DATA_DIRS points, the handbuilt one will suffer from 
duplicate tapset searches.

One possible fix is to mark up the standard tapset directory with some magic
file that prevents it from being searched via the $XDG_DATA_DIRS path.  OTOH
that could defeat the purpose, if an auxiliary package installs tapset files
under the same path.
Comment 1 Mark Wielaard 2011-01-27 08:18:23 UTC 
See also the discussion in this thread:
http://sourceware.org/ml/systemtap/2011-q1/msg00115.html
Comment 2 Mark Wielaard 2011-01-27 08:19:38 UTC 
(In reply to comment #0)
> One possible fix is to mark up the standard tapset directory with some magic
> file that prevents it from being searched via the $XDG_DATA_DIRS path.  OTOH
> that could defeat the purpose, if an auxiliary package installs tapset files
> under the same path.

Urgh. Hadn't thought of that. Maybe we really should split "system" and "application" tapsets into separate include paths then.
Comment 3 Frank Ch. Eigler 2012-12-20 15:31:51 UTC 
commit 43179f1055