Call for help: where the hell is the full documentation of RPM headers

(28)

Do you develop a website? It is infinitely better to synchronize live and development sites using the PEAR Installer

(25)

doing the PEAR thing

(19)

Using PEAR 1.4.0 to install PEAR packages on a remote host

(19)

PEAR now fits in a bottle: meet go-pear.phar

(17)

Syndicate This Blog

RSS 0.91 feed

RSS 1.0 feed

RSS 2.0 feed

ATOM 0.3 feed

ATOM 1.0 feed

RSS 2.0 Comments

Powered by

Serendipity PHP Weblog

Saturday, October 8. 2005

Call for help: where the hell is the full documentation of RPM headers

I am trying to fix up the pear makerpm command so that something like the following English is possible

"Package X conflicts with (Package Y > 1.5 and Package Y < 1. or (Package Y > 1.8 and Package Y < 2.0)"

However, after literally an hour searching through google, through the linux documentation project, and so on, I still haven't found a SINGLE page of documentation that actually describes in detail all of the possible settings for the Conflicts: tag. What I do know is:

it's the same as the Requires: tag
you can use "or" to join related conditions
you can use commas to separate different conditions
or, you can use Conflicts0 Conflicts1 etc.

This is all I can find. WHERE IS THE STUPID DOCUMENTATION! @# !@ @!

Posted by Greg Beaver in PHP at 08:21 | Comments (3) | Trackbacks (0)

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

Do not know if the list is still active but you may ask there:
rpm-list-request@redhat.com to subscribe
and rpm-list@ to post.

#1 Pierre on 2005-10-08 10:09 (Reply)

Hi Greg,

did you have a look at the newly created rpmreader pecl extension yet? You can probably find out more about the RPM headers there or from the author.

#2 Mike on 2005-10-08 11:14 (Reply)

http://www.redhat.com/docs/books/max-rpm/max-rpm-html/s1-rpm-depend-manual-dependencies.html:

"The conflicts tag has the same format as requires. It accepts a real or virtual package name and can optionally include version and release specifications or a serial number."

HTH.

#3 Martin Jansen (Homepage) on 2005-10-08 11:32 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	Standard emoticons like :-) and ;-) are converted to images. E-Mail addresses will not be displayed and will only be used for E-Mail notifications To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above: BBCode format allowed You can use [geshi lang=lang_name [,ln={y\|n}]][/lang] tags to embed source code snippets
	Remember Information? Subscribe to this entry
Submitted comments will be subject to moderation before being displayed.