[MPlayer-cvslog] CVS: main/DOCS/tech binary-packaging.txt, 1.1, 1.2
The Wanderer
inverseparadox at comcast.net
Wed Dec 29 16:31:48 CET 2004
Dominik 'Rathann' Mierzejewski wrote:
>> While it is acceptable to provide packages optimized for specific CPUs,
>> you MUST provide at least one "lowest common denominator" package set
>>-that will work on all CPUs. This means it MUST be configured with
>>+that will work on all CPUs. This means it MUST be configured with the
>> --enable-runtime-cpudetection option. Building for specific CPUs requires
>> disabling this option, but try to make sure that users cannot accidentally
>> install a package not suitable for their CPU. With RPMs, for example, this
>>-is handled automatically, when building with "--target arch" rpm option.
>>+is handled automatically, when building with the "--target arch" rpm option.
> ^^^
>> You SHOULD provide an option to rebuild the package with full debug
>> information enabled (by passing --enable-debug=3 to ./configure and
>> disabling any stripping of binaries and libs during the build process).
>>-For example my source RPM can be rebuilt with "--with debug" option, which
>>+For example my source RPM can be rebuilt with a "--with debug" option, which
> ^^^
>
> This is inconsistent. The second one should be the definite article,
> too, shouldn't it?
Not necessarily. I read the latter as "my source RPM is such that there
exists a --with debug option which" et cetera (with the implication
being that there is not necessarily such an option for every source
RPM), whereas with the former it sounds like the --target arch option
exists in any case for every source RPM. If either part of that is
inaccurate, then one or the other probably should be changed, but...
--
The Wanderer
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
A government exists to serve its citizens, not to control them.
More information about the MPlayer-cvslog
mailing list