snapcraft 2.27 has been released

Roberto Mier Escandón  roberto.escandon at canonical.com
Tue Feb 28 14:00:48 UTC 2017


Other thing I've seen, the environment set there does not affect the
stop command. Is there any way to do it? Am I doing anything wrong?.

Cheers.

On 28/02/17 14:51, Roberto Mier Escandón  wrote:
> Hey guys,
> 
> Couldn't we have environment property pointing also to a file script as
> in the case of scriptlets. In the case of needing to set a bunch of
> things before launching app I'd prefer having it in that way.
> 
> Cheers.
> 
> On 24/02/17 20:05, Kyle Fazzari wrote:
>>
>>
>> On 02/24/2017 10:49 AM, Claudio André wrote:
>>>
>>> 2017-02-17 10:49 GMT-02:00 Sergio Schvezov
>>> <sergio.schvezov at canonical.com <mailto:sergio.schvezov at canonical.com>>:
>>>
>>>     Hello snapcrafters!
>>>
>>>     ## Setting up environment
>>>
>>>     No more wrapper scripts just to setup on environment entry, this is
>>>     now tied into an app entry in `apps`. Here's a quick example:
>>>
>>>     ```yaml
>>>     apps:
>>>         vim:
>>>             command: bin/vim
>>>             environment:
>>>                 VIMRUNTIME: $SNAP/share/vim/vim80
>>>     ```
>>>
>>>
>>> Hi, I tried to append to path (see below). It is not supported. 
>>>
>>> ```yaml
>>>     environment:
>>>       PATH: "$SNAP/usr/lib/jvm/default-java/bin:$PATH" 
>>> ```
>>>
>>> I'm ok with it. But, in case this is not by design, I'm mailing you guys.
>>
>> I can verify this. To clarify, this builds and runs fine, but actually
>> results in the PATH including the string `$PATH` instead of expanding it.
>>
>> Can a snapd dev comment on this? Is that intended?
>>
>>
>>




More information about the Snapcraft mailing list