On Friday 12 August 2005 02:49, Paweł Sakowski wrote: > On Fri, 2005-08-12 at 00:25 +0300, Elan Ruusamäe wrote: > > > There were some small changes in macros, so no need to fake. Will > > > bumping rpm_macros_rev in rpm.spec and changing BR: rpm-build to > > > BR: rpmbuild(macros) be sufficient? How does that work with backporting > > > to AC-branch? > > > > yes. true. it won't work until it's really backported. (ie the BR could > > be satisfied but the actual behaviour not) > > > > so perhaps rpmbuild(monoautodeps) is the right choice. > > No need to introduce a Provides for every single new feature. > rpm_macros_rev high enough has always served that purpose. If you're > concerned that someone will bump macros rev on Ac again without > backporting the mono changes, mark that as a TODO in AC-branch spec. > Then again, if you're modifying it, you might port the change altogether > as well.
hmm. what about just creating new package rpm-monoprov and requiring that package on BR? $ rpm -qa | grep prov rpm-perlprov-4.4.1-5 rpm-pythonprov-4.4.1-5 -- glen _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
