[arch-multilib] Permission to move package into multilib
speps at gmx.com
Mon Sep 20 23:50:28 EDT 2010
On Mon, Sep 20, 2010 at 05:43:32PM -0500, Brad Fanella wrote:
> On Mon, Sep 20, 2010 at 4:43 PM, Jan Steffens <jan.steffens at gmail.com>wrote:
> > On Mon, Sep 20, 2010 at 10:52 PM, Brad Fanella <bradfanella at archlinux.us>
> > wrote:
> > > Hi guys,
> > >
> > > I have a package (bin32-chuck) that needs to me moved to multilib, as the
> > developer currently has no native source for x86_64. I hope this is the
> > correct place to ask, but could I have "permission" (for my user) to submit
> > that package to multilib?
> > >
> > > Thanks,
> > > Brad
> > > _______________________________________________
> > > arch-multilib mailing list
> > > arch-multilib at archlinux.org
> > > http://mailman.archlinux.org/mailman/listinfo/arch-multilib
> > 3 votes? Seems obscure.
> > On the other hand, it adds no dependencies and isn't very large.
> > In any case, it would need to be properly compiled using gcc-multilib.
> > The PKGBUILD on AUR does not do that and uses the old, broken scheme
> > of repackaging i686 packages.
> > _______________________________________________
> > arch-multilib mailing list
> > arch-multilib at archlinux.org
> > http://mailman.archlinux.org/mailman/listinfo/arch-multilib
> Chuck is in [community]. The developers upstream were having problems with
> x86_64, so only i686 is available for compilation.
> On Mon, Sep 20, 2010 at 4:47 PM, Ionut Biru <biru.ionut at gmail.com> wrote:
> > in addition i would prefer adding proper support for x86_64 to the actual
> > chuck PKGBUILD instead using bin32-chuck name.
> I could do that if you like. Would that be the better option in this
> arch-multilib mailing list
> arch-multilib at archlinux.org
I have updated the bin32-chuck PKGBUILD according to the multilib system.
I think now it could be adopted for an inclusion.
More information about the arch-multilib