[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to manage symbolic links ?



* Alexis Sukrieh <spam@sukria.net> [030813 14:58]:
> The first software I try to debianize needs to be placed in
> /usr/share/appname and then to link the binary to /usr/bin which makes
> something like this :
> 
> ln -s /usr/share/appname/appname /sur/bin/appname

Has this to be this way? In general having things to be called in
some bin/ dir might be nicer. (And might even make some rule-based
things easier for people using something like SELinux or mounting
/usr/share noexec.)

> For instance, my Makefile.am looks like :
> $(LN_S) -f $(DESTDIR)${coredir}/appname $(DESTDIR)$(bindir)/appname;
> 
> and the link appname-x/debian/tmp/usr/bin/appname points to
> /home/me/debian_devel/appname-x/debian/tmp/usr/share/appname/appname
> 
> 
> How can I manage to have a symbolic link installed with a good path ?

If a link is the way to go, you can either: remove the code from the
Makefile and put its generation to debian/rules. Or you could make
it relative. (link to ../bla/blub)

> If I remove $(DESTDIR) in Makefile.am and Makefile.in, the link is no
> more installed...

This sounds strange. Links to nonexistent positions should normaly
be no problem. Did I understood you right, that you changed it so:
$(LN_S) -f ${coredir}/appname $(DESTDIR)$(bindir)/appname;

(Hm, shouldn't bindir be the bin-dir? this looks more like it makes
 the link the other way around...)

Hochachtungsvoll,
  Bernhard R. Link

-- 
Sendmail is like emacs: A nice operating system, but missing
an editor and a MTA.



Reply to: