On Sat, Jun 2, 2012 at 7:11 PM, Torsten Veller wrote:
> * Corentin Chary :
>> On Thu, May 17, 2012 at 2:02 AM, Kent Fredric wrote:
>> > On 13 May 2012 07:43, Torsten Veller wrote:
>> >> It doesn't even list "Moose" for Moose?
>> >
>> > Its probably falling outside the initial 10 results, I forgo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey all - I'd like to propose that enewuser forces updates to a user's
home dir and shell whenever it is called, so that if this changes with
new versions of an ebuild it is dealt with automatically rather than
having to modify them in pkg_postinst/p
On Mon, 11 Jun 2012 15:42:25 +0200
Agostino Sarubbo wrote:
> would be great if everyone runs repoman before file the stable
> request.
Generally, yes.
> In particular, many times, happens that are required other ~arch
> packages, so a small check like this, should be enough:
>
> for i in x86 a
On Wed, 13 Jun 2012 18:58:40 +0200
Jeroen Roovers wrote:
> > for i in x86 amd64 hppa $and_other_arches ;do ekeyword $i
> > $ebuild;done
>
> ekeyword $(ARCHES) ${EBUILD}
Or even go wild and do
ekeyword all ${EBUILD}
I don't know how well that magically works (as expected) in different
scenar
On Wednesday 13 June 2012 18:58:40 Jeroen Roovers wrote:
> ekeyword $(ARCHES) ${EBUILD}
>
> Saves time.
Yep, good example.
> > repoman manifest
> > repoman commit -p -m "foo"
>
> Why would you commit the changes when you only intended to check
> deps before filing a stabilisation request?
-p
On Wed, 13 Jun 2012 12:00:16 -0400
Ian Stakenvicius wrote:
> + ### force updates of some user properties
> + usermod -d "${ehome}" "${euser}" || die
> + usermod -s "${eshell}" "${euser}" || die
I think usermod can handle multiple arguments.
--
Best reg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 01:19 PM, Michał Górny wrote:
> On Wed, 13 Jun 2012 12:00:16 -0400 Ian Stakenvicius
> wrote:
>
>> + ### force updates of some user properties +
>> usermod -d "${ehome}" "${euser}" || die + usermod
>> -s "$
On 13-06-2012 12:00:16 -0400, Ian Stakenvicius wrote:
> Hey all - I'd like to propose that enewuser forces updates to a user's
> home dir and shell whenever it is called, so that if this changes with
> new versions of an ebuild it is dealt with automatically rather than
> having to modify them in p
On 6/13/2012 12:00 PM, Ian Stakenvicius wrote:
> Hey all - I'd like to propose that enewuser forces updates to a user's
> home dir and shell whenever it is called, so that if this changes with
> new versions of an ebuild it is dealt with automatically rather than
> having to modify them in pkg_post
On 06/13/2012 09:18 PM, Mike Gilbert wrote:
On 6/13/2012 12:00 PM, Ian Stakenvicius wrote:
Hey all - I'd like to propose that enewuser forces updates to a user's
home dir and shell whenever it is called, so that if this changes with
new versions of an ebuild it is dealt with automatically rather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 02:18 PM, Mike Gilbert wrote:
> On 6/13/2012 12:00 PM, Ian Stakenvicius wrote:
>> Hey all - I'd like to propose that enewuser forces updates to a
>> user's home dir and shell whenever it is called, so that if this
>> changes with new vers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 02:09 PM, Fabian Groffen wrote:
> On 13-06-2012 12:00:16 -0400, Ian Stakenvicius wrote:
>> Hey all - I'd like to propose that enewuser forces updates to a
>> user's home dir and shell whenever it is called, so that if this
>> changes with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 01:21 PM, Ian Stakenvicius wrote:
> On 13/06/12 01:19 PM, Michał Górny wrote:
>> On Wed, 13 Jun 2012 12:00:16 -0400 Ian Stakenvicius
>> wrote:
>
>>> + ### force updates of some user properties +
>>> usermod -d "${ehome}"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 02:45 PM, Ian Stakenvicius wrote:
> On 13/06/12 01:21 PM, Ian Stakenvicius wrote:
>> On 13/06/12 01:19 PM, Michał Górny wrote:
>>> On Wed, 13 Jun 2012 12:00:16 -0400 Ian Stakenvicius
>>> wrote:
>
+ ### force updates
On 6/13/2012 2:32 PM, Ian Stakenvicius wrote:
> On 13/06/12 02:09 PM, Fabian Groffen wrote:
>> On 13-06-2012 12:00:16 -0400, Ian Stakenvicius wrote:
>>> Hey all - I'd like to propose that enewuser forces updates to a
>>> user's home dir and shell whenever it is called, so that if this
>>> changes w
On Wednesday 13 June 2012 14:32:22 Ian Stakenvicius wrote:
> On 13/06/12 02:09 PM, Fabian Groffen wrote:
> > On 13-06-2012 12:00:16 -0400, Ian Stakenvicius wrote:
> >> Hey all - I'd like to propose that enewuser forces updates to a
> >> user's home dir and shell whenever it is called, so that if th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 03:04 PM, Mike Frysinger wrote:
>
> we have egetshell and egethome already. thus it's fairly easy to
> detect the transition case. if they installed the older version
> which set values that you now want to change: if has_version
> ' e
On Wednesday 13 June 2012 15:11:19 Ian Stakenvicius wrote:
> On 13/06/12 03:04 PM, Mike Frysinger wrote:
> > we have egetshell and egethome already. thus it's fairly easy to
> > detect the transition case. if they installed the older version
> > which set values that you now want to change: if ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 03:14 PM, Mike Frysinger wrote:
>
> eset{home,shell} don't exist today, so you should implement them
> :) -mike
RFC - heavily based on enewuser.
- --- user.eclass [some timestamp]
+++ user.eclass.esethome [some other timesta
On Wednesday 13 June 2012 15:35:40 Ian Stakenvicius wrote:
> --- user.eclass [some timestamp]
> +++ user.eclass.esethome [some other timestamp]
> @@ -388,3 +388,63 @@
> }
>
> fi
> +
> +# @FUNCTION: esethome
has to be inside the giant if block. so put this above the "fi".
> +# @USAG
Good evening,
As per bug #421037, there is a demand to make multiple voicemail storage
backends switchable within the ebuild. The USE_EXPAND mechanism would
automatically provide an explanation of the selections being made (as
opposed to overloading USE=odbc in what seems to me a non-obvious way).
21 matches
Mail list logo
