On Fri, 2008-02-29 at 17:14 -0500, seth vidal wrote: > On Fri, 2008-02-29 at 23:02 +0100, Ralf Corsepius wrote: > > On Fri, 2008-02-29 at 16:50 -0500, Tom "spot" Callaway wrote: > > > On Fri, 2008-02-29 at 14:48 -0700, Orion Poplawski wrote: > > > > It might me useful to have a %bits macro automatically set to 32 or 64 > > > > as appropriate. Does this seem useful or is there a better way? > > > > > > I'm not aware of a better way, this would be quite useful IMHO. > > > > A better way would be to rewrite any code requiring such tricks to not > > require them. > > > > In modern C/C++ there hardly is any need for such band-aids (cf. > > stdint.h, inttypes.h, limits.h) > > But this would be handy if we can use it during the build. > > We could do little tricks like: > > Requires: foo.%bits > Provides: foo.%bits > > and it would let us get rid of multilib file-requires like: > > /usr/lib[64]/libgcj.so.9 Why would this be helpful? All you do this way, is to replace one "natural/direct" "Requires/Provides" with another, "artificial/indirect"" one. I don't see how this would be helpful. Ralf -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
