On 2007-11-09 14:55:16 -0700, Brad Nicholes wrote:
> >>> On 11/9/2007 at 2:29 PM, in message
> <[EMAIL PROTECTED]>, "Bernard Li"
> <[EMAIL PROTECTED]> wrote:
> > Hi Brad:
> > 
> > On 11/9/07, Carlo Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote:
> > 
> >> http://fedoraproject.org/wiki/Packaging/Python 
> > 
> > If it's okay with you, I will follow the instructions in the wiki docs
> > to add the .pyc files to the RPM.
> > 
> > Cheers,
> > 
> > Bernard
> 
> I'm still a little concerned about doing that because I'm not sure
> that it solves any real problem.  I would rather just clean up the
> python directory completely rather than deliver .pyc files.  In a
> standard case, the .py files from one package might be put down in the
> same location as another package's .py files.  In this case if the
> first package has to uninstall, it would obviously have to know which
> .pyc files it owns.  In our case, we own the directory where the .py
> and .pyc files are located.  I think it would be easier and safer to
> just remove the directory.  But do whatever you believe is best.
> 

sadly rpm doesnt work this way. if the .pyc files are not in the %files
list the directory will not be deleted. that means you have to track
them at least as %ghost entries. given that building the .pyc files
during the build is rather simple. we could just ship them in the rpms

which is imho done on all distros.

    darix

-- 
          openSUSE - SUSE Linux is my linux
              openSUSE is good for you
                  www.opensuse.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to