Packaging question: conflicting binaries

[Aaron Bennett]

Hello,

I'm packaging the "Pyro" python library, from 
sourceforge.net/projects/pyro, and it includes several sample scripts. 
Unfortunately, one of them is called "esd."

How should I deal with this?  Unfortunately, making it not install them 
at all requires a hack to pyro's setup.py; installing them in a 
different place is easy.  Is there a fedora.us custom about installing 
sample python scripts as part of python libraries?  Should they go into 
/usr/share/doc/python-pyro/examples? 

Any ideas are appreciated.

- Aaron


-- 
Aaron Bennett
UNIX Administrator
Franklin W. Olin College of Engineering

[Ville Skyttä]

On Tue, 2004-08-24 at 18:38, Aaron Bennett wrote:

>  I'm packaging the "Pyro" python library, from 
>  sourceforge.net/projects/pyro, and it includes several sample scripts. 
>  Unfortunately, one of them is called "esd."
>  
>  How should I deal with this?  Unfortunately, making it not install them 
>  at all requires a hack to pyro's setup.py; 
%install
[...]
rm -f $RPM_BUILD_ROOT{_bindir}/[not-wanted-stuff]

(or use %exclude in %files) ?

>   installing them in a 
>  different place is easy.  Is there a fedora.us custom about installing 
>  sample python scripts as part of python libraries?  Should they go into 
>  /usr/share/doc/python-pyro/examples?  
Personal opinion: is/are the script(s) really useful as anything but
examples?  If not, I'd install them as %doc, if yes, perhaps rename the
conflicting ones to eg. pyro-esd.

[Aaron Bennett]

Ville Skyttä wrote:

> Personal opinion: is/are the script(s) really useful as anything but
> examples?  If not, I'd install them as %doc, if yes, perhaps rename the
> conflicting ones to eg. pyro-esd.
>   
>  
In fact, I just found out that one of the scripts is a daemon, called 
interestingly enough, esd.  Of course that's a questionable decision by 
the author's part, since there ought to be a script for /etc/init.d, 
etc, but the fact is I need to package this stuff up.  I'm going to put 
the binaries into /usr/bin/python-pyro and email the author with a 
suggestion or two.



-- 
Aaron Bennett
UNIX Administrator
Franklin W. Olin College of Engineering

[Jeff Pitman]

On Wednesday 25 August 2004 22:31, Aaron Bennett wrote:
>  I'm going to put
>  the binaries into /usr/bin/python-pyro and email the author with a
>  suggestion or two. 
How about renaming to "pyro-esd" including the potential sysv script?

-- 
-jeff