On Tue, 2009-09-29 at 14:45 +0200, Michael Schwendt wrote: [...] > > But what about a provide statement (guess it's the same)? > > No. See e.g. the automatic library SONAME provides: libfoo.so.0 > Or see "rpm -qa --provides". Good point. > > In case it is also illegal what would be the best to do. Will yum update > > the package if a user installed previously "myapp.pl" instead of "myapp" > > and the new package does not have a provide statement anymore? > > Yes, because the newer "myapp" package will replace the older one, > regardless of its Provides. That was the behavior of yum I expected/hoped to see. > > In the > > end the question would be should I follow the guidelines or provide > > backward compatibility in sense of updating. > > > > cheers > > Stefan > > > > PS: ".pl" should indicate that it is a Perl script, not a locale. > > Try: repoquery --whatrequires myapp.pl > > If nothing uses this virtual package name (and it isn't used upstream > either), get rid of it. No other package uses this name (also not upstream) so I'm going to remove it. Thanks for clarification, Stefan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
