[pacman-dev] [PATCH 03/11] makepkg: do not attempt to strip arch agnostic packages
aepd87 at gmail.com
Thu Jun 17 11:51:26 EDT 2010
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.
And if namcap has such checks, why not makepkg?
It just gets very tedious to mantain a makepkg-ng on the side.
More information about the pacman-dev