[csw-maintainers] merge issue with 64-bit builds (was [csw-pkgsubmissions] newpkgs libproxy)

[Maciej (Matchek) Blizinski]

2010/3/22 Philip Brown <phil at bolthole.com>:
> On Mon, Mar 22, 2010 at 1:00 PM, Maciej (Matchek) Blizinski
> <maciej at opencsw.org> wrote:
>
>> How do you go about discriminating between the executables (scripts or
>> binaries) to be or not to be included in the resulting package?
>
> Any automated method of doing this, is guaranteed to occasionsally be flawed.
> To just take the example of "devel" packages:
> Sometimes, if a devel package is pure text, you might assume that it's
> arch independant.
>
> Except when it has v9 or other 64bit flags in configs.

Yes, and it's easy to detect these cases.

> Or, perhaps it has size-of-int tricks and assumptions

These might be harder to detect.

> Or, ....
>
> It basically comes down to human judgement eventually.
>
> So you might just choose to make it easier for humans to quickly and
> efficiently divide the files as appropriately.

Do I read you correctly that you're questioning the feasibility of
automation in this area by arguing that "it might fail"?