[pacman-dev] [PATCH 03/11] makepkg: do not attempt to strip arch agnostic packages
git at nezmer.info
Thu Jun 17 16:59:31 EDT 2010
On Thu, Jun 17, 2010 at 11:21:26AM -0430, Andres P wrote:
> On Thu, Jun 17, 2010 at 10:56 AM, Dan McGee <dpmcgee at gmail.com> wrote:
> > On Thu, Jun 17, 2010 at 9:55 AM, Andres P <aepd87 at gmail.com> wrote:
> >> On Thu, Jun 17, 2010 at 9:56 AM, Dan McGee <dpmcgee at gmail.com> wrote:
> >>> This is one of those "seems like a good idea but why" patches. Yes,
> >>> we'll save milliseconds in building a package, but what if someone has
> >>> a legit reason for putting libraries or binaries in an 'any' package?
> >>> I'm going to -1 this one.
> >> But "any" means that there's no arch dependant code in the package?
> > No, it means the package is able to be installed on any architecture
> > and work as intended. What if I had an "elf-demo" package that
> > contained different ELF files from multiple architectures? Yes,
> > contrived, but possible.
> And for that corner case, people that have split in the opts array
> have to run it against -any packages that, suffice to say, are
> probably not going to benefit from the exception.
> So you're creating a what if for the least possible scenario.
It's not a hard-to-imagine corner case. Remember that we are talking
i[3-6]86 and x86_64 here. The latter is capable of running the former
binaries (As far as the IS is concerned).
Some OSes still use i386 low level tools (e.g for booting) in
x86_64/AMD64 systems. That's just one example.
Some projects use self-contained wine. That's another example.
I can provide more examples if you wish.
More information about the pacman-dev