[arch-multilib] Permission to move package into multilib
snowmaniscool at gmail.com
Fri Oct 8 10:58:30 EDT 2010
On Thu, Oct 7, 2010 at 11:01 PM, Brad Fanella <bradfanella at archlinux.us> wrote:
> On Oct 7, 2010, at 9:51 PM, Eric Bélanger <snowmaniscool at gmail.com> wrote:
>> On Thu, Oct 7, 2010 at 10:00 PM, Brad Fanella <bradfanella at archlinux.us>
>>> On Tue, Oct 5, 2010 at 7:39 PM, Eric Bélanger <snowmaniscool at gmail.com>
>>>> I believe he wants you to add x86_64 support to the chuck PKGBUILD in
>>>> community. See how it's done for skype. Just commit the change to
>>>> the PKGBUILD in trunk and he'll build it (I guess).
>>> That doesn't seem right...
>>> If anyone wants a working PKGBUILD, simply use bin32-chuck PKGBUILD
>>> that SpepS was nice enough to write up. .
>>> I don't understand how we can add x86_64 support to chuck as both
>>> lib32-gcc-libs and lib32-libsndfile are dependencies.
>>>  http://aur.pastebin.com/TdDUYhD4
>>> Truly sorry if I am missing something here.
>>> Thanks a ton,
>> Did you checked how it's done for skype or wine? Use conditional
>> if [[ $CARCH == i686 ]]; then
>> depends=('gcc-libs' 'libsndfile')
>> depends=('lib32-gcc-libs' 'lib32-libsndfile')
>> and so on.
>>> arch-multilib mailing list
>>> arch-multilib at archlinux.org
>> arch-multilib mailing list
>> arch-multilib at archlinux.org
> Yep. That's exactly how I did it.
> Sorry 'bout that. I wasn't thinking straight. I took a look at the lib32
> dependencies and automatically assumed that it needed to be placed into
> multilib' completely disregarding the fact that they are simply build-time
Actually, it depends on lib32 packages so the x86_64 chuck package
must go in multilib. I see you already put a package in community.
You can leave it there for the time being. Someone with access to
multilib can easily move it to multilib repo.
> arch-multilib mailing list
> arch-multilib at archlinux.org
More information about the arch-multilib