On Tue, Jul 7, 2015 at 5:20 PM, Frederik “Freso” S. Olesen <
freso...@gmail.com> wrote:
> If you build both versions (which is the default for `makepkg` IIRC),
> you will need to delete the downloaded source midway through or makepkg
> will complain that "$pkgname-$pkgver" (x86_64) doesn't match i
On 07/07, Frederik “Freso” S. Olesen wrote:
Den 26-06-2015 kl. 02:21 skrev Hugo Osvaldo Barrera:
On Thu, Jun 25, 2015, at 12:50, Maxime Gauduin wrote:
On Thu, Jun 25, 2015 at 5:27 PM, Doug Newgard
wrote:
On Thu, 25 Jun 2015 12:15:01 -0300
Hugo Osvaldo Barrera wrote:
Why not just name them t
Den 26-06-2015 kl. 02:21 skrev Hugo Osvaldo Barrera:
> On Thu, Jun 25, 2015, at 12:50, Maxime Gauduin wrote:
>> On Thu, Jun 25, 2015 at 5:27 PM, Doug Newgard
>> wrote:
>>> On Thu, 25 Jun 2015 12:15:01 -0300
>>> Hugo Osvaldo Barrera wrote:
Why not just name them the same locally?
>>>
>>> That
On Thu, Jun 25, 2015, at 12:50, Maxime Gauduin wrote:
> On Thu, Jun 25, 2015 at 5:27 PM, Doug Newgard
> wrote:
>
> > On Thu, 25 Jun 2015 12:15:01 -0300
> > Hugo Osvaldo Barrera wrote:
> >
> > >
> > >
> > > Why not just name them the same locally?
> > >
> > > source_i686=("$pkgname-$pkgver::
>
On Thu, 25 Jun 2015 20:40:13 +0200, Ralf Mardorf wrote:
>Sorry, I didn't follow the whole thread, so perhaps this is useless,
>but maybe not:
>
>https://aur.archlinux.org/packages/pa/palemoon-bin/PKGBUILD
My apologies, now I read the whole thread. I should have done it before
sending my mail.
Sorry, I didn't follow the whole thread, so perhaps this is useless,
but maybe not:
https://aur.archlinux.org/packages/pa/palemoon-bin/PKGBUILD
On 25-06-2015 18:07, Patrick Burroughs (Celti) wrote:
>
> A quick google and some personal testing showed me that the former
> doesn't work and the latter does, because bash doesn't interpolate
> variables in the middle of another variable like that; you need to use
> eval to make a second pass fo
On Thu, Jun 25, 2015 at 12:07 PM, Patrick Burroughs
wrote:
> On Thu, 25 Jun 2015 17:01:02 +0200 Johannes Löthberg
> wrote:
>
> > On 25/06, Patrick Burroughs wrote:
> > >On Thu, 25 Jun 2015 13:17:49 +0100 Mauro Santos
> > > wrote:
> > >> Wouldn't just
> > >>
> > >> local tarball="${source_$CARCH[
On Thu, 25 Jun 2015 17:01:02 +0200 Johannes Löthberg
wrote:
> On 25/06, Patrick Burroughs wrote:
> >On Thu, 25 Jun 2015 13:17:49 +0100 Mauro Santos
> > wrote:
> >> Wouldn't just
> >>
> >> local tarball="${source_$CARCH[0]}"
> >>
> >> or something very similar do the job?
> >
> >I believe you need
On Mon, Jun 22, 2015 at 11:46 PM, Bruno Pagani
wrote:
> Le 14/06/2015 16:31, Johannes Löthberg a écrit :
> > On 14/06, Johannes Löthberg wrote:
> >> On 14/06, Reventlov wrote:
> In which way is it cleaner and more structured? It's a bash hack
> instead of actually using properly structu
On Thu, Jun 25, 2015 at 5:27 PM, Doug Newgard
wrote:
> On Thu, 25 Jun 2015 12:15:01 -0300
> Hugo Osvaldo Barrera wrote:
>
> >
> >
> > Why not just name them the same locally?
> >
> > source_i686=("$pkgname-$pkgver::
> http://example.com/release-${pkgver}-i386.tar.gz";)
> > md5sums_i686=('ffeeddc
On Thu, 25 Jun 2015 12:15:01 -0300
Hugo Osvaldo Barrera 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://e
On Thu, Jun 25, 2015, at 08:26, Martti Kühne wrote:
> Do this:
>
> source_i686=("http://example.com/release-${pkgver}-i386.tar.gz";)
> md5sums_i686=('ffeeddccbbaa99887766554433221100')
> source_x86_64=("http://example.com/release-${pkgver}-x86_64.tar.gz";)
> md5sums_x86_64=('00112233445566778899
On 25/06, Patrick Burroughs wrote:
On Thu, 25 Jun 2015 13:17:49 +0100 Mauro Santos
wrote:
Wouldn't just
local tarball="${source_$CARCH[0]}"
or something very similar do the job?
I believe you need:
local tarball=$(eval "echo \${source_${CARCH}[0]}")
Why do you believe that?
--
Sincerel
On 25/06, Ralf Mardorf wrote:
However, AFAIK Ubuntu does not provide i386, even if the packages should
be named like that, IIRC they only provide i486, so the time will come
when even i686 is history.
Linux does not have support for i386 anymore.
--
Sincerely,
Johannes Löthberg
PGP Key ID: 0
On Thu, 25 Jun 2015 13:17:49 +0100 Mauro Santos
wrote:
> On 25-06-2015 12:26, Martti Kühne wrote:
> > Do this:
> >
> > source_i686=("http://example.com/release-${pkgver}-i386.tar.gz";)
> > md5sums_i686=('ffeeddccbbaa99887766554433221100')
> > source_x86_64=("http://example.com/release-${pkgver}-
PS: I guess I still own an unused PC with a Cyrix CPU. Taking a look at
the Wiki, it might be that even this Cyrix CPU could belong to the 486
CPUs. My Atari ST has got parallel to the 68000 CPU a 80286 CPU, but I
only run TOS and similar and DR DOS on that machine, not Linux ;).
Le 25/06/2015 14:26, Ralf Mardorf a écrit :
> On Thu, 25 Jun 2015 14:18:49 +0200, Bruno Pagani wrote:
>> The best option would be to get ride of i686. :p
> Likely an issue for Arch Linux freaks in Third World nations. Btw. I'm
> from Germany and still own a
> "fall-back"-"you-never-know"-32-bit-arc
On Thu, 25 Jun 2015 14:18:49 +0200, Bruno Pagani wrote:
>The best option would be to get ride of i686. :p
Likely an issue for Arch Linux freaks in Third World nations. Btw. I'm
from Germany and still own a
"fall-back"-"you-never-know"-32-bit-architecture-mobo. Even my 64-bit
architecture computer
Le 25/06/2015 13:26, Martti Kühne a écrit :
> Do this:
>
> source_i686=("http://example.com/release-${pkgver}-i386.tar.gz";)
> md5sums_i686=('ffeeddccbbaa99887766554433221100')
> source_x86_64=("http://example.com/release-${pkgver}-x86_64.tar.gz";)
> md5sums_x86_64=('00112233445566778899aabbccddeef
On 25-06-2015 12:26, Martti Kühne wrote:
> Do this:
>
> source_i686=("http://example.com/release-${pkgver}-i386.tar.gz";)
> md5sums_i686=('ffeeddccbbaa99887766554433221100')
> source_x86_64=("http://example.com/release-${pkgver}-x86_64.tar.gz";)
> md5sums_x86_64=('00112233445566778899aabbccddeeff'
Do this:
source_i686=("http://example.com/release-${pkgver}-i386.tar.gz";)
md5sums_i686=('ffeeddccbbaa99887766554433221100')
source_x86_64=("http://example.com/release-${pkgver}-x86_64.tar.gz";)
md5sums_x86_64=('00112233445566778899aabbccddeeff')
package() {
local tarball="${source_i686[0]}"
Le 23/06/2015 01:02, Eli Schwartz a écrit :
> On Mon, Jun 22, 2015 at 4:46 PM, Bruno Pagani
> wrote:
>
>> I’m not sure to understand you. How would you package this one for
>> instance:
>>
>> https://aur4.archlinux.org/packages/chromium-pepper-flash-standalone/
>>
>> ?
>>
>> Bruno
>>
> See this di
On Mon, Jun 22, 2015 at 4:46 PM, Bruno Pagani
wrote:
> I’m not sure to understand you. How would you package this one for
> instance:
>
> https://aur4.archlinux.org/packages/chromium-pepper-flash-standalone/
>
> ?
>
> Bruno
>
See this diff: http://pastebin.com/EggVuYpH
-- Eli Schwartz
Le 14/06/2015 16:31, Johannes Löthberg a écrit :
> On 14/06, Johannes Löthberg wrote:
>> On 14/06, Reventlov wrote:
In which way is it cleaner and more structured? It's a bash hack
instead of actually using properly structured and supported features.
>>>
>>> Please take this not-a-bu
On 14/06, Johannes Löthberg wrote:
On 14/06, Reventlov wrote:
In which way is it cleaner and more structured? It's a bash hack
instead of actually using properly structured and supported features.
Please take this not-a-bug https://bugs.archlinux.org/task/43714 in
consideration, too.
It's wh
On 14/06, Reventlov wrote:
In which way is it cleaner and more structured? It's a bash hack
instead of actually using properly structured and supported features.
Please take this not-a-bug https://bugs.archlinux.org/task/43714 in
consideration, too.
It's why i'm not using this structure, pers
Hello.
Le Sun, 14 Jun 2015 15:51:02 +0200,
Johannes Löthberg a écrit :
>
> In which way is it cleaner and more structured? It's a bash hack
> instead of actually using properly structured and supported features.
>
Please take this not-a-bug https://bugs.archlinux.org/task/43714 in
consideratio
On 14/06, Νῖκος Θεοδώρου wrote:
On Sat, 13 Jun 2015 22:57:45 +0200
Johannes Löthberg wrote:
On 13/06, Νῖκος Θεοδώρου wrote:
>I do it like that and mksrcinfo works fine:
>
>if [ "$CARCH" = "i686" ]; then
>source=(…)
>md5sums=(…)
>elif [ "$CARCH" = "x86_64" ]; then
>source=(…)
>md5sums=(…)
>fi
>
On Sat, 13 Jun 2015 22:57:45 +0200
Johannes Löthberg wrote:
> On 13/06, Νῖκος Θεοδώρου wrote:
> >I do it like that and mksrcinfo works fine:
> >
> >if [ "$CARCH" = "i686" ]; then
> >source=(…)
> >md5sums=(…)
> >elif [ "$CARCH" = "x86_64" ]; then
> >source=(…)
> >md5sums=(…)
> >fi
> >
>
> Even if
On 13/06, Νῖκος Θεοδώρου wrote:
I do it like that and mksrcinfo works fine:
if [ "$CARCH" = "i686" ]; then
source=(…)
md5sums=(…)
elif [ "$CARCH" = "x86_64" ]; then
source=(…)
md5sums=(…)
fi
Even if it works it should not be done anymore. makepkg has had support
for architecture-specific sou
On Sat, 13 Jun 2015 20:31:08 +0200
Rudy Matela wrote:
> if [ ${CARCH} = 'x86_64' ]; then
> source=("http://example.com/release-${pkgver}-x86_64.tar.gz";)
> md5sums=('00112233445566778899aabbccddeeff')
> else
> source=("http://example.com/release-${pkgver}-i386.tar.gz";)
> md5sums=('ffeeddccbbaa99
On Sat, Jun 13, 2015 at 2:31 PM, Rudy Matela wrote:
> Hello,
>
> I am importing a PKGBUILD for something that has only a binary release.
> More specifically, a binary release for i686 and another for x86_64.
>
> In the old AUR, I was packaging it using an if clause to choose which
> release to dow
Hello,
I am importing a PKGBUILD for something that has only a binary release.
More specifically, a binary release for i686 and another for x86_64.
In the old AUR, I was packaging it using an if clause to choose which
release to download depending on the architecture -- this way, I can
have a sin
34 matches
Mail list logo
