Jon Gough wrote:
The user install plugins can vary between very simple with a config file
and a couple of icons up to complex with large data >1GB and hundreds of
icons.
So, if debs must not touch files in $HOME but is allowed to create files
there (is that not a contradiction?) where else co
james frize wrote:
However, I can't open a file from /usr/share via my python script as I
don't have permission to open files in a protected directory
print "loading links.txt from usr/share/doc/gtk-link-lizard..."
try:
self.text_file =
open("usr/shar
Ignacio Valdes wrote:
Required to produce versions for both rpm and deb. No introspection
means not easy to convert this from rpm to deb which is where this
started. This would make it much easier to produce both deb and rpm
versions if it has the ability to introspect those variables.
If all
The Fungi wrote:
I'm not sure I've seen what seems to me to be the obvious solution
come through in a reply yet, but why not just create a custom chroot
for your target distribution (be it RHEL 4 or SUSE 9 or whatever)
and build in there?
Apparently this works pretty well for most people. If s
[This is probably the wrong list for this.]
Ek Zindagoi wrote:
I would like to build rpms on a debian system for use on a redhat
system. Can I do that on a debian system ?
In short, no; system libraries on a RedHat system likely have different
versions (and soversions), as well as a few dif
5 matches
Mail list logo
