On 08/09/2016 10:24 AM, Enrico Joerns wrote:
On 08/09/2016 07:17 AM, Anders Darander wrote:
* Enrico Jorns [160808 15:55]:
Constructing the USERADD_PARAM_${PN} value with += (as done before)
resulted in having a whitespace added for each entry not having its
PACKAGECONFIG parameter activated.
On 08/09/2016 07:17 AM, Anders Darander wrote:
* Enrico Jorns [160808 15:55]:
Constructing the USERADD_PARAM_${PN} value with += (as done before)
resulted in having a whitespace added for each entry not having its
PACKAGECONFIG parameter activated.
This is not only a cosmetical issue. The us
* Enrico Jorns [160808 15:55]:
> Constructing the USERADD_PARAM_${PN} value with += (as done before)
> resulted in having a whitespace added for each entry not having its
> PACKAGECONFIG parameter activated.
> This is not only a cosmetical issue. The useradd class concatenates all
> useradd comma
On Mon, Aug 8, 2016 at 6:37 AM, Enrico Jorns wrote:
> Constructing the USERADD_PARAM_${PN} value with += (as done before)
> resulted in having a whitespace added for each entry not having its
> PACKAGECONFIG parameter activated.
>
> This is not only a cosmetical issue. The useradd class concatena
Constructing the USERADD_PARAM_${PN} value with += (as done before)
resulted in having a whitespace added for each entry not having its
PACKAGECONFIG parameter activated.
This is not only a cosmetical issue. The useradd class concatenates all
useradd commands from all subpackages of a package by d
