On Mon, May 10, 2004 at 08:57:55PM -0400, seth vidal alleged: > On Mon, 2004-05-10 at 16:24 +0100, Steve Hill wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > The attached patch against yum 2.0.6 adds an excludedocs option. > > Specifying "excludedocs=1" in the confid file makes yum exclude the docs > > from the rpm install (like rpm --excludedocs). > > > > It doesn't work on some badly written RPMs which either don't mark the > > docs as documentation or expect the docs to always be installed, but > > that's a problem with the RPMs themselves, not with yum. > > So, your patch is fine - but I'm trying to figure out where to draw the > line for options like these. I understand excludedocs - but if > excludedocs comes in, why not --nodeps or --replacefiles? > > I'm wondering if it wouldn't be worthwhile to have a yum rpm macros file > so anything that anyone wants to set for the default yum rpm transaction > set flags can be set there and not clutter up the yum config file with > rpmts-specific actions. > > Thoughts? I've not tested this, but would adding "%_excludedocs 1" to your ~/.rpmmacros have the same effect? -- Garrick Staples, Linux/HPCC Administrator University of Southern California -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.dulug.duke.edu/pipermail/yum/attachments/20040510/58b7f470/attachment.bin
