On Tue, Feb 18, 2003, Andrews, Martin wrote:
To follow up - I also run into this problem when I install an RPM from
current and then later want to go back to the main release (say when current
changes have been merged back to an update of the main openpkg release).
I have added an -e option,
Just looking for suggestions on:
1. Naming the root dir of an openpkg installation?
I was initially considering something like DIR/opkg/VERSION with a
symlink to it, such as DIR/opkg/prod
e.g.$root = /opt/opkg/1.2
/opt/opkg/prod - /opt/opkg/1.2
However, if it's safe to assume 1.x
Vinod,
Don't have experience with your other questions but I have been creating
modified RPM's. I have been replacing the release with my own version that
has a prefix for my organization and then an incrementing version number -
starting as lion.1 in this case. I don't think the release I based
Martin,
Thanks for the quick reply 8-)
How does that affect upgrades, i.e. between versions, does rpm and/or
openpkg-tool recognize the concept of newer if the version/release is
not a number? (Sorry ... that's something I haven't read up on ... it's
probably in the RPM HOWTO)
I was hoping for
Vinod,
Then probably just append the .orgname.number to the existing release
number. This will make the resulting rpm seem newer than the release you
based it on but less then the next release. Though I am guessing you don't
want to automatically upgrade to the next release from the original
I am trying to control my openpkg services (with cfengine) and just noticed
that the rc script does not return an error code when the action fails - it
just prints a warning. What's up with that? I want to know if my start
fails, or get an error when status finds the service is not running. Adding
On Tue, Feb 18, 2003, Andrews, Martin wrote:
Hi,
I am trying to control my openpkg services (with cfengine) and just noticed
that the rc script does not return an error code when the action fails - it
just prints a warning. What's up with that? I want to know if my start
fails, or get an
