James Bowes wrote:
Jeremy Katz wrote:
I can see a few options:
1) Bail on moving things. Kind of sucks as moving things would get us a
lot more consistency.
2) In the %post of the yum package, move everything around. This breaks
verification of the packages containing repo files and leads to lots of
rpmnew junk peppered across the filesystem
3) In the %post of the yum package, just move the config file. Ensure
that we look at both /etc/yum/repos.d and /etc/yum.repos.d. Packages
that contain repo configs need to deal with managing their own
migration.
4) ???
I like 3. I don't think we want to mess with files that come from other
rpms. What we should do is write a good script bit for %post, and make
it available for the packagers of these repo configs.
We could also spew out a warning when a file is in the old location.
This might help spur packagers along but will probably just result in
many duplicate bugs upon your plate, Mr. Katz.
-James
+1
Tim
_______________________________________________
Yum-devel mailing list
Yum-devel@linux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
