LD_LIBRARY_PATH not set via a wrapper anymore?
Gustavo Niemeyer
gustavo.niemeyer at canonical.com
Wed May 18 14:49:52 UTC 2016
https://bugs.launchpad.net/snapcraft/+bug/1583204
On Wed, May 18, 2016 at 11:47 AM, Gustavo Niemeyer <
gustavo.niemeyer at canonical.com> wrote:
>
> This is extremely unexpected and error prone behavior. It should be a
> command of its own, snap-content or similar.
>
> On Wed, May 18, 2016 at 11:34 AM, Kyle Fazzari <kyle.fazzari at canonical.com
> > wrote:
>
>> On 05/18/2016 10:24 AM, Gustavo Niemeyer wrote:
>> >
>> > I'm probably misunderstanding. Are you saying that the behavior of
>> > "snapcraft snap <directory>" is completely different from the behavior
>> > of "cd <directory>; snapcraft snap"?
>>
>> Yes, you understand correctly. `snapcraft snap` (or just `snapcraft`)
>> will look for a `snapcraft.yaml` and go through snapcraft's lifecycle of
>> pull, build, stage, strip, and snap. Whereas `snapcraft snap
>> <directory>` is the new `snappy build`, where it just snaps up the
>> directory provided. This is used for OS snaps and other situations where
>> one wants to write the `snap.yaml` and other metadata by hand.
>>
>> --
>> Kyle Fazzari (kyrofa)
>> Software Engineer
>> Canonical Ltd.
>> kyle at canonical.com
>>
>>
>
>
> --
> gustavo @ http://niemeyer.net
>
--
gustavo @ http://niemeyer.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160518/df327563/attachment.html>
More information about the snappy-devel
mailing list