[crux-devel] pkgutils: INSTALL rule support

Tilman Sauerbeck tilman at crux.nu
Tue Aug 29 20:38:54 UTC 2006


Tilman Sauerbeck [2006-08-25 15:56]:
> [...]
> The documentation hasn't been updated yet, but if anyone wants to try

I attached a patch to the pkgadd man page. Do you think this is good
enough?

Thanks,
Tilman

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
Index: pkgadd.8.in
===================================================================
--- pkgadd.8.in	(revision 1762)
+++ pkgadd.8.in	(working copy)
@@ -32,13 +32,7 @@
 .B "\-h, \-\-help"
 Print help and exit.
 .SH CONFIGURATION
-When using \fBpkgadd\fP in upgrade mode (i.e. option -u is used) the
-file \fI/etc/pkgadd.conf\fP will be read. This file can contain rules describing
-how pkgadd should behave when doing upgrades. A rule is built out of three
-fragments, \fIevent\fP, \fIpattern\fP and \fIaction\fP. The event describes
-in what kind of situation this rule applies. Currently only one type of event is
-supported, that is \fBUPGRADE\fP. The pattern is a regular expression and the action
-applicable to the \fBUPGRADE\fP event is \fBYES\fP and \fBNO\fP. More than one rule of the same
+\fBpkgadd\fP is configured by the file \fI/etc/pkgadd.conf\fP. This file can contain rules, that are built out of three fragments: \fIevent\fP, \fIpattern\fP and \fIaction\fP. The event describes in what kind of situation this rule applies. Currently there are two types of events, these are \fBUPGRADE\fP and \fBINSTALL\fP. \fBUPGRADE\fP rules are applied when a package is installed over an existing version, and \fBINSTALL\fP rules are applied in any case. The pattern is a regular expression. The action applicable to both the \fBUPGRADE\fP and \fBINSTALL\fP event is \fBYES\fP and \fBNO\fP. More than one rule of the same
 event type is allowed, in which case the first rule will have the lowest priority and the last rule
 will have the highest priority. Example:
 
@@ -51,7 +45,7 @@
 
 The above example will cause pkgadd to never upgrade anything in /etc/ or /var/log/ (subdirectories included),
 except files in /etc/X11/ (subdirectories included), unless it is the file /etc/X11/XF86Config.
-The default rule is to upgrade everything, rules in this file are exceptions to that rule.
+The default rule is to upgrade/install everything, rules in this file are exceptions to that rule.
 (NOTE! A \fIpattern\fP should never contain an initial "/" since you are referring to the files in the
 package, not the files on the disk.)
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20060829/6d6a5899/attachment.asc>


More information about the crux-devel mailing list