hi, as all mingw32-x packages BuildRequires: mingw32-filesystem wouldn't be possible to automatically add it somehow to all packages? on the other hand should this BR be version? in case of automatic R is version then yes, but then each time the mingw32-filesystem package update we've to update each mingw32-x spec file which is a nightmare!:-(
On Wed, Nov 26, 2008 at 01:51:43PM +0100, Farkas Levente wrote:
hi, as all mingw32-x packages BuildRequires: mingw32-filesystem wouldn't be possible to automatically add it somehow to all packages? on the other hand should this BR be version? in case of automatic R is version then yes, but then each time the mingw32-filesystem package update we've to update each mingw32-x spec file which is a nightmare!:-(
No we don't.
Each MinGW package should depend on mingw32-filesystem >= VERSION where VERSION is the minimum version required.
For example, if some feature was added to mingw32-filesystem version 40 in order to support mingw32-foo -- for example, if an extra 'Provides(somedll)' was added to support mingw32-foo -- then mingw32-foo would have:
BuildRequires: mingw32-filesystem >= 40
and would stay like that until another feature was added to support mingw32-foo (if that ever happened).
Rich.
Richard W.M. Jones wrote:
On Wed, Nov 26, 2008 at 01:51:43PM +0100, Farkas Levente wrote:
hi, as all mingw32-x packages BuildRequires: mingw32-filesystem wouldn't be possible to automatically add it somehow to all packages? on the other hand should this BR be version? in case of automatic R is version then yes, but then each time the mingw32-filesystem package update we've to update each mingw32-x spec file which is a nightmare!:-(
No we don't.
Each MinGW package should depend on mingw32-filesystem >= VERSION where VERSION is the minimum version required.
For example, if some feature was added to mingw32-filesystem version 40 in order to support mingw32-foo -- for example, if an extra 'Provides(somedll)' was added to support mingw32-foo -- then mingw32-foo would have:
BuildRequires: mingw32-filesystem >= 40
and would stay like that until another feature was added to support mingw32-foo (if that ever happened).
but in mingw32-filesystem's mingw32-find-requires.sh: echo 'mingw32-filesystem >= @VERSION@' which means any mingw32-x packages will require mingw32-filesystem latest installed, but BR mingw32-filesystem >= 40. is it ok?
On Wed, Nov 26, 2008 at 02:40:35PM +0100, Farkas Levente wrote:
but in mingw32-filesystem's mingw32-find-requires.sh: echo 'mingw32-filesystem >= @VERSION@' which means any mingw32-x packages will require mingw32-filesystem latest installed, but BR mingw32-filesystem >= 40. is it ok?
Yes - this just ensures that the _runtime_ requires is always the actual version that it was built against. The _build_ requires should only be bumped when some change is made to mingw32-filesystem which affects the package.
You might be better off trying to find a counterexample where the scheme we have in place now might fail.
Rich.
-
Farkas Levente -
Richard W.M. Jones