Peter Volkov wrote:
> Steve, your example only tests how much time bash takes to parse string.
> It's obvious that in quoted strings some expansions could be avoided and
> thus bash works faster.
Yeah that's all I wanted to get across.
> But although ebuilds use bash syntax they are
> interprete
On Mon, 13 Oct 2008 03:59:00 +0100
Steve Long <[EMAIL PROTECTED]> wrote:
> Thomas Sachau wrote:
>
> > what about this:
> > insinto /usr/share/doc/${P}/examples
> Is there any chance we can start using correctly quoted filenames
> across the board?
This is correctly quoted, so, yep.
--
gcc-por
Steve Long wrote:
insinto /usr/share/doc/${P}/examples
Is there any chance we can start using correctly quoted filenames across the
board?
Since when is ${P} allowed to have spaces?
Besides being faster (quote the whole thing)
Have you done a benchmark certifying that "/usr/share/doc/${P}
Thomas Sachau wrote:
> what about this:
> insinto /usr/share/doc/${P}/examples
Is there any chance we can start using correctly quoted filenames across the
board?
[EMAIL PROTECTED] NB: I'm raising this as a talking-point, not pushing it as an
agenda,
so please don't reply if discussion doesn't
On Sun, 5 Oct 2008 21:48:09 +0200
Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> All our documentation (devmanual, ebuild howto, skel.ebuild, pms)
> recommends "econf || die".
I've fixed PMS.
--
Ciaran McCreesh
signature.asc
Description: PGP signature
> On Sun, 05 Oct 2008, Thomas Sachau wrote:
>> econf \
>> [...]
>> ${myconf} || die
> "|| die" could be dropped
All our documentation (devmanual, ebuild howto, skel.ebuild, pms)
recommends "econf || die".
So maybe you should first make an effort to have it changed there?
I wouldn't consider
Ali Polatel (hawking) schrieb:
> use threads \
> && myconf="${myconf} --with-threads" \
> || myconf="${myconf} --without-threads"
What about an econf option $(use_with threads)?
> econf \
> --with-fpectl \
> --enable-shared \
>
