"Claes Bäckström" <claes.backstrom@gmail.com> writes:
On 1/19/07, Andreas Jaeger <aj@suse.de> wrote:
"Claes Bäckström" <claes.backstrom@gmail.com> writes: [...]
And also thinks that a pattern should not depend on rpm packages that other rpm packages included in the pattern also depends on, as there is no need for that. This is not a problem technical speaking it's just harder to maintain and confusing to people.
I'm not sure I understand you here. Could you rephrase this, please?
Well I can try to explain what I mean with an example. (names as so on is just imagination)
Say we have a backup pattern. Something like this: ---- securebackup (the tool that does the backups) tar bzip2 openssh ---
The securebackup tool uses tar and bzip2 to do the backup then scp it to another server. This means that securebackup rpm depends on tar, bzip2 and openssh.
In my meaning the backup pattern is wrong. It should only depend on securebackup as that will install tar, bzip2 and openssh. This means when securebackup is dead upstreams and no one will fork it. It's very simple to change the backup pattern to depend on gnubackup that uses tar, gzip and ssh instead. No need to change the backup pattern removing bzip2 and adding gzip to it.
I hope this example explains what I was talking about.
Then we agree completely. I might not have done it consequently in my patterns, so you find redundancy, please tell me and I fix it ;-) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126