Re: SPECS: tao.spec - auto mono prov/req

2005-08-12 Thread Elan Ruusamäe
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
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: SPECS: tao.spec - auto mono prov/req

2005-08-12 Thread Bartosz Taudul
On Fri, Aug 12, 2005 at 10:29:55PM +0300, Elan Ruusamäe wrote:
 what about just creating new package rpm-monoprov and requiring that package 
 on BR?
What should be in that package? macros.* are provided by rpm-build and
mono-find-* are from mono.

wolf
-- 
  Bartek   .  - Kto tam śpi?
  Taudul   :  
  .:
w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: SPECS: tao.spec - auto mono prov/req

2005-08-11 Thread Bartosz Taudul
On Thu, Aug 11, 2005 at 10:42:24PM +0300, Elan Ruusamäe wrote:
 i believe proper way of doing it is require some rpmbuild(macros) version 
 (don't forget to document it in PLD-doc/BuildRequires.txt), in case someone 
 backports it to ac-branch 4.4.1 version of rpm
Almost all changes are in rpm's code, not in macros, so I don't see how
it could work. Maybe some BR: rpm(monodep) would be better?

wolf
-- 
  Bartek   .  - Wiecie o czym są Chłopi Reymonta?
  Taudul   :  - O chłopach.
  .:
w o l f @ p l d - l i n u x . o r g.:. http://wolf.valkyrie.one.pl/
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: SPECS: tao.spec - auto mono prov/req

2005-08-11 Thread Elan Ruusamäe
On Thursday 11 August 2005 23:29, Bartosz Taudul wrote:
 On Thu, Aug 11, 2005 at 10:42:24PM +0300, Elan Ruusamäe wrote:
  i believe proper way of doing it is require some rpmbuild(macros) version
  (don't forget to document it in PLD-doc/BuildRequires.txt), in case
  someone backports it to ac-branch 4.4.1 version of rpm

 Almost all changes are in rpm's code, not in macros, so I don't see how
 it could work. Maybe some BR: rpm(monodep) would be better?
...or fake revision for it:
$ cvs ci -f -m '- rev 1.234 for mono dep' rpm.macros

 wolf
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: SPECS: tao.spec - auto mono prov/req

2005-08-11 Thread Elan Ruusamäe
On Friday 12 August 2005 00:17, Bartosz Taudul wrote:
 On Fri, Aug 12, 2005 at 12:05:16AM +0300, Elan Ruusamäe wrote:
   Almost all changes are in rpm's code, not in macros, so I don't see how
   it could work. Maybe some BR: rpm(monodep) would be better?
 
  ...or fake revision for it:
  $ cvs ci -f -m '- rev 1.234 for mono dep' rpm.macros

 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.

 wolf

-- 
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en