On Mon, 2005-07-11 at 14:08 +0200, Valentin David wrote:
> On 7/11/05, Eelco Visser visser@cs.uu.nl wrote:
> > > libexecdir = $(exec_prefix)/libexec/$(subdir)
> >
> > That’s great! Only remaining problem is with XTC; the Makefile.xt rules
> > will register the tool as ‘run’ at location $(libexecdir) instead of
> > registering $(subdir)/run at location $(exec_prefix)/libexec.
>
> But here, libexecdir is $(exec_prefix)/libexec/$(subdir).

Yes, the problem is not that the registration is wrong, but that we now
get the following registrations:

in directory core/run

run -> $(exec_prefix)/libexec/core/run

in directory int/run

run -> $(exec_prefix)/libexec/int/run

So the problem is that the names of the tools as registered in XTC,
i.e., the keys in the XTC table are the same in the two cases. What I
would like is

in directory core/run

core/run/run -> $(exec_prefix)/libexec/core/run

in directory int/run

int/run/run -> $(exec_prefix)/libexec/int/run

This would reflect the subdir namespace. But maybe it would be better if
we could declare an XTC namespace. For instance, declare in the
Makefile.am

in directory core/run

libexecdir = $(exec_prefix)/libexec/$(PACKAGE_NAME)/$(subdir)
XTC_NS = $(PACKAGE_NAME)/core

tfa/core/run -> $(exec_prefix)/libexec/core/run/run

in directory int/run

libexecdir = $(exec_prefix)/libexec/$(PACKAGE_NAME)/$(subdir)
XTC_NS = $(PACKAGE_NAME)/run

we get the XTC registration:

tfa/int/run -> $(exec_prefix)/libexec/int/run/run

Now, the problem is that `xtc register’ insists on using the filename of
the tool as the key in the XTC table.

There should be a new style registration which allows different names.
I’ll make that an issue for 0.15.1 (since it has much to do with
modularization and namespaces).

Submitted on 24 July 2005 at 23:39

STR-359, martin:
This is a duplicate of issue:
https://catamaran.labs.cs.uu.nl/jira/browse/STR-337

I don’t understand why this is an issue for 0.15.1 (bugs): modularization and namespaces is 0.18?

STR-359, anya:
The attached Makefile.xt seems to take care of this problem (for some cases). It works by adding the directory name to the tool name. If you want components installed in $(pkglibexecdir)/$(subdir), simply do:

pkglibexecdir = $(libexecdir)/$(PACKAGE)/$(subdir)
INSTALL_SUBDIR_PKGLIBEXEC=$(subdir)/

etc.

STR-359, martin:
AFAIK, that solution will break every single XTC tool … If I understand Eelco’s suggestion correctly, then there should be an optional specifcation of a namespace ($XTC_NS) that is used to qualify the tools, independent of its relative location in a package. I think that is a good idea, and it doesn’t break anything as long as $XTC_NS is not used.