Jo Rhett wrote:
On Jul 24, 2007, at 11:32 AM, Eric Searcy wrote:Problem statement: I would like to append package versions and an comparison operator to the name that is passed to BuildCommandLine. If you read the next sentence after the one you quoted above, I mention it could be done in package.c if we redesigned the function to take the pointer to the structure, instead of elements of the structure. Which way do you think would be the best way to do this:After reading your patch in detail I'm fairly positive that this isn't the right approach. Sorry, forgive the frankness. It certainly would make nice shorthand for maching a specific version:mypackage action=install version=2.12 cmp=lt However, it would make the following impossible: mypackage-2.12 action=install version=2.0 cmp=lt
Just as a bit of additional information (not taking sides either way here), there are some RPM package names that may be ambiguous.
For example, there are the infamous 'db' packages, frequently named "db3", "db4", and so on, in addition to having a version string. From one of my CentOS4 systems:
[EMAIL PROTECTED] ~]$ rpm -q db4 db4-4.2.52-7.1 There are some packages that are even worse: [EMAIL PROTECTED] ~]$ rpm -q compat-libgcc-296 compat-libstdc++-296 compat-libgcc-296-2.96-132.7.2 compat-libstdc++-296-2.96-132.7.2The package names are actually "compat-libgcc-296" and "compat-libstdc++-296". You would have to somehow disambiguate the "296" as being part of the package name, instead of a version string.
Just something to ponder, in case it affects any of the code. -- Jesse Becker NHGRI Linux support (Digicon Contractor)
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Bug-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/bug-cfengine
