The Linux version of ACPICA is completely different from what is available on the ACPICA
website. The native ACPICA code is translated to Linux with a utility at the time ACPICA
is integrated into Linux (this is done for every new release of the ACPICA code.)
So, I'm not sure what your goal is.
From: Nathan O. [mailto:[email protected]
Sent: Wednesday, June 02, 2010 1:33 PM
To: Moore, Robert
Subject: Re: [Devel] Packaging
The source code wouldn't be changed at all, I am not programmer. I try
to package software for the Arch Linux community repo for others to use.
All it does it pull from the software's site and compile it and install.
If it does get moved to the official repo then when it compiles the
software it will put in binary form.
On 06/02/2010 03:30 PM, Moore, Robert wrote:
> The original ACPICA source must retain the original Intel ACPICA license,
> Only the converted-for-linux gets the GPL license.
> Intel license:
> * 3. Conditions
> * 3.1. Redistribution of Source with Rights to Further Distribute
> * Redistribution of source code of any substantial portion of the
> * Code or modification with rights to further distribute source must
> * the above Copyright Notice, the above License, this list of
>> -----Original Message-----
>> From: Nathan O. [mailto:[email protected]
>> Sent: Wednesday, June 02, 2010 1:27 PM
>> To: Moore, Robert
>> Subject: Re: [Devel] Packaging
>> On 06/02/2010 03:24 PM, Moore, Robert wrote:
>>> Please explain what you mean by "package the source"
>>>> -----Original Message-----
>>>> From: devel-bounces(a)acpica.org [mailto:[email protected]
>>>> Of Nathan O.
>>>> Sent: Wednesday, June 02, 2010 1:19 PM
>>>> To: devel(a)acpica.org
>>>> Subject: [Devel] Packaging
>>>> I was wondering if I would be allowed to package the source for acpica
>>>> while including the license file from
as part of the
>>>> Thought I'd ask before doing this in case there would be any issues.
>>>> Devel mailing list
>> The packaging would be similar to
>> Unless it gets moved from AUR to the main repo as a binary form. Though
>> I'd copy the License page's text and include it as a License file so a
>> user could read the license, like the license would be put in