[aur-general] [AUR4] Single binary package for different architectures

Hugo Osvaldo Barrera hugo at barrera.io
Fri Jun 26 00:21:06 UTC 2015



On Thu, Jun 25, 2015, at 12:50, Maxime Gauduin wrote:
> On Thu, Jun 25, 2015 at 5:27 PM, Doug Newgard <scimmia at archlinux.info>
> wrote:
> 
> > On Thu, 25 Jun 2015 12:15:01 -0300
> > Hugo Osvaldo Barrera <hugo at barrera.io> wrote:
> >
> > >
> > >
> > > Why not just name them the same locally?
> > >
> > > source_i686=("$pkgname-$pkgver::
> > http://example.com/release-${pkgver}-i386.tar.gz")
> > > md5sums_i686=('ffeeddccbbaa99887766554433221100')
> > > source_x86_64=("$pkgname-$pkgver::
> > http://example.com/release-${pkgver}-x86_64.tar.gz")
> > > md5sums_x86_64=('00112233445566778899aabbccddeeff')
> > >
> > > package() {
> > >   tar xf $pkgname-$pkgver
> > >   ...
> > > }
> > >
> >
> > That creates problems verifying the checksums.
> >

What problems exactly?

> 
> Exactly, read a couple emails back. Also why would you want to decompress
> the source tarball in the package function? The source for your
> particular
> arch, and only that one, is already decompressed by bsdtar [...]

I'm aware of this, it was an awful example really. the important bit was
really that you wouldn't need to deal with the discrepancies manually.

-- 
Hugo Osvaldo Barrera


More information about the aur-general mailing list