Just want to know if there is any suggested guidelines for linking
a script file in /usr/bin path. I see some of packages that installs
the python script files have a wrapper script written and installed in
/usr/bin. Is there any issue of directly linking that python script
file in /usr/bin?
... since I'm not going to be there, due to an unavoidable conflict.
Sorry folks, but as of right now, we didn't have any pending tickets, so
it would have been a short meeting. :)
Lets just meet again on Nov 23, or, if something urgent comes up in the
interim, feel free to meet without me (assuming that you have quorum).
I'm about to package Tine 2.0 (http://www.tine20.org/) and almost have a
package ready for review. One open issue I would like to clarify in
advance is, if I should consider the ZendFramework for PHP a library
which should not be bundled according to ?
At present the package is shipping it's own copy of the ZendFramework as
delivered with the original Tine 2.0 tarball, but I could remove that
and require the php-ZendFramework package instead.
Please let me know what you think about this.
Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D
I am seeking some advice on the correct way to drop a patch that changes
the name of the default configuration file for monit.
In Fedora, we carry a patch for monit that changes upstream's default
configuration filename from /etc/monitrc to /etc/monit.conf.
Other than the fact that we have always carried the patch, I found no
reason to carry it. Even though it is a small patch, in order to stay as
close as possible to upstream, I want to drop it (and another one) in
The question is how to do this nicely. I see several options:
a) just drop the patch, breaking existing installations until the admin
renames his configuration file, which will be annoying during F16 -> F17
b) moving a possibly existing /etc/monit.conf to /etc/monitrc in %post
c) symlinking /etc/monit.conf to /etc/monitrc if it exists in %post
d) moving a possibly existing /etc/monit.conf to /etc/monitrc and symlink
it back to /etc/monit.conf
e) keep carrying the patch
Can someone give me some pointers here? Whichever option I choose, I'd add
a README.Fedora to explain the change to the RPM.
EB11 5E56 E648 9D99 E8EF 05FB C513 6FD4 1302 B48A
I'm trying to package perl-Data-Dumper (RHEL4 and RHEL5), and rpmlint is returning the following warning:
perl-Data-Dumper.x86_64: W: private-shared-object-provides /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/auto/Data/Dumper/Dumper.so Dumper.so()(64bit)
How can I correct this behavior?
Nelson Manuel O. Marques