-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Here's the version 2 with the fixed author information. I forgot to
send the initial email to the PR team, so doing that now. Will commit
in 72 hours if there are no objections.
- --
Title: LastPass package migration
Author: Göktürk Yüksek
Author
On 16 May 2016 14:17, rindeal wrote:
> So this is what it looks like now:
still missing tests. see eclass/tests/flag-o-matic.sh.
> - local f var findflag="$1"
> -
> - # this code looks a little flaky but seems to work for
> - # everything we want ...
> - # for example, if CFLAGS="-march=
On 18 May 2016 22:25, aide...@gentoo.org wrote:
> awk doesn't have the -i option like sed and if editing file in place is
> desired, additional steps are required. eawk uses tmp file to make it
> look to the caller editing happens in place.
what's your real use case ? i've never once thought "man
On 20 May 2016 02:16, Mart Raudsepp wrote:
> I would like if such a function would explicitly document that calling
> this function means the caller should DEPEND on an awk provider.
> Similarly, I would like that all ebuild that call 'sed' actually DEPEND
> on sed, not just half of them.
> I would
On 05/19/2016 07:51 AM, Jeroen Roovers wrote:
> Perhaps it's a good idea to add a section to the devmanual about adding
> new keywords to packages.
>
> Recruits in particular might benefit from some background on what
> keywording means and when it should be done, especially before they
> start ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Mart Raudsepp:
> Ühel kenal päeval, K, 18.05.2016 kell 22:25, kirjutas
> aide...@gentoo.org:
>> From: Amadeusz Żołnowski
>>
>> awk doesn't have the -i option like sed and if editing file in
>> place is desired, additional steps are required. eawk
Ühel kenal päeval, K, 18.05.2016 kell 22:25, kirjutas
aide...@gentoo.org:
> From: Amadeusz Żołnowski
>
> awk doesn't have the -i option like sed and if editing file in place
> is
> desired, additional steps are required. eawk uses tmp file to make it
> look to the caller editing happens in place.
On Thu, May 19, 2016 at 10:50:48PM +0100, Amadeusz Żołnowski wrote:
> "Robin H. Johnson" writes:
> > 1.
> > If your AWK command has an error, then this clobbers the file, a
> > better variant, with die, would be:
> > awk "$@" "$f" >"${tmpf}" || die "awk failed..."
> > cp -f "${tmpf}" "$f" || die "
"Robin H. Johnson" writes:
> 1.
> If your AWK command has an error, then this clobbers the file, a
> better variant, with die, would be:
> awk "$@" "$f" >"${tmpf}" || die "awk failed..."
> cp -f "${tmpf}" "$f" || die "copy back failed"
Thanks! On the one hand it's a simple function, and on the ot
Ulrich Mueller writes:
> Yes, of course. "|| die -n || return" if you want the function to
> return at that point, if it was called under nonfatal.
>
>> https://blogs.gentoo.org/mgorny/2015/11/13/the-ultimate-guide-to-eapi-6
>
> Note that the ${?} in the code example there is redundant.
Why redun
> On Thu, 19 May 2016, Mart Raudsepp wrote:
>> Ulrich Mueller writes:
>> > The EAPI 6 method would be to use "|| die -n". Then the caller
>> > either call "eawk" if the function should die automatically, or
>> > "nonfatal eawk" if it should return with an error status.
> Don't you possibly n
Ühel kenal päeval, N, 19.05.2016 kell 18:51, kirjutas Amadeusz
Żołnowski:
> Ulrich Mueller writes:
> > The EAPI 6 method would be to use "|| die -n". Then the caller can
> > either call "eawk" if the function should die automatically, or
> > "nonfatal eawk" if it should return with an error status
Ulrich Mueller writes:
> The EAPI 6 method would be to use "|| die -n". Then the caller can
> either call "eawk" if the function should die automatically, or
> "nonfatal eawk" if it should return with an error status.
Yes, that seems better. Hasn't it been introduced earlier than in
EAPI 6?
--
On Thu, May 19, 2016 at 10:51 AM, Jeroen Roovers wrote:
> Perhaps it's a good idea to add a section to the devmanual about adding
> new keywords to packages.
>
> Recruits in particular might benefit from some background on what
> keywording means and when it should be done, especially before they
Perhaps it's a good idea to add a section to the devmanual about adding
new keywords to packages.
Recruits in particular might benefit from some background on what
keywording means and when it should be done, especially before they
start maintaining packages and then realise their packages are so
> On Wed, 18 May 2016, Amadeusz Żołnowski wrote:
>> Also, wouldn't the absence of 'die' cause silent breakages?
> I want to caller decide whether die or not and what error messge to
> give.
The EAPI 6 method would be to use "|| die -n". Then the caller can
either call "eawk" if the function
Dear Pallav,
how about using a dedicated eclass for arch-testing?
E.g., you might provide a function in some eclass
that only runs when called from pkg_postinst [1]
phase AND when some configuration option is set.
Then a maintainer / arch tester might provide
the tests inside the ebuild director
This is a continuation of "[gentoo-dev] Proposal for changes for the next
EAPI
version" thread. Since the former subject isn't very relevant anymore.
Target:
A place to provide scripts that can be used by an automated arch-tester bot
to
stabilize Gentoo packages. These scripts can be as simple as
18 matches
Mail list logo
