Why are akmod packages arch specific?

[Orcan Ogetbil]

On Sat, Apr 24, 2010 at 3:56 PM, Stewart Adam wrote:
> On 2010/04/24 8:16 AM, Thorsten Leemhuis wrote:
>>
>> But here is another thought I wanted to bring up for discussion months
>> ago: I think it might be easier to build the akmod packages from a
>> separate source package. That way we avoid the flipping the "%define
>> buildforkernels newest" macro when updating the package, which quickly
>> is forgotten, confuses people (afaics), and makes things harder for the
>> one that is pushing the packages and cleaning up old kmod packages in
>> the repos.
>>
>> The downsides: When updating the kmod (e.g. to a newer version or when
>> integrating a new patch) the maintainer would have to copy the
>> foo-kmod.spec file and all the sources to a different directory and flip
>> a bit (the name or a macro). That's a bit more work for the packager,
>> but more "natural" and hence might be easier for everyone.
>>
>> Opinions?
>
> +1. I think this is more intuitive and copying the spec if not a big deal
> anyways - just 'cvs diff -u' then 'patch < /path/to/diff' wherever needed.
>

+1 from me too. This sounds like the most unambiguous solution. It
will probably require some changes in kmodtool and a rewrite of the
guidelines though.

Orcan