rently unsupported, per
https://bugs.launchpad.net/bugs/1616507 .
The issue pre-dates the command aliases feature, so the rationales
forbidding them have probably changed.
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
ugs.launchpad.net/bugs/1677974
I don't know the time frame. I'm primarily interested in Launchpad
building my snaps, which will also need updating once snapcraft can
somehow handle snap package build dependencies.
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
ot be seen or cause conflicts if I use the
/usr/bin/python3, which is what I'm suggesting is an improvement. And
they will not be seen by or cause conflicts with snaps using the
content interface, no matter if they are confined or classic, which is
also a good thing because they will be e
on and the system python will
coexist better (as there is no risk of snap python finding a package
built by system python and vice versa). I have no idea if
sitecustomize.py could do this though, and suspect it might involve
patching.
(do classic snaps actually have $SNAP_*DATA?)
--
S
pts
located anywhere. And snaps using the interface would remain contained
as they are. Assuming we are allowed to mix interfaces and classic
confinement :)
But now I think on it further, its probably not a good idea to pollute
the main python snap when it is being used as a dependency.
--
Stuart
ould stick to using virtualenvs outside of the snap for this,
assuming a modern enough Python.
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
(but look at 'jq' if you insist on shell scripts - it seemed very helpful
for dealing with json)
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
ment is cleaned?
I think this will affect all classic snaps that need to run subprocesses,
such as screen, vim, tmux... with other wrapper variables like the LD_*
settings leaking :-(
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcra
as
supposed to have been fixed with 2.18.
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
On 12 January 2017 at 11:33, Stuart Bishop <stuart.bis...@canonical.com>
wrote:
>
> On 12 January 2017 at 02:31, Charles Butler <charles.but...@canonical.com>
> wrote:
> You don't have much control over the generated systemd service file. Its
> an open issue. So whi
Maybe you could handle this by monitoring the files opened
by the build process somehow?
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
s sooner rather than later since pgbouncer is another app that
refuses to run as root. I wasn't looking forward to documenting how to
manually install systemd service definitions :)
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
;> >
>> > slots:
>> > test-share:
>> > content: test-content-server
>> > interface: content
>> > write:
>> > - .
>> >
>> > When accessing from client side snap, it shows "permission denied".
>>
>>
>>
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
ry
processes by pointing to someone elses pid file or overwriting arbitrary
files by logging somewhere it shouldn't.
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
structure to declare
what additional connections need to be made after installation of the snap.
I'd like to get this right the first time since I'm going to be stuck with
it.
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify se
t mention the magic name(s) needed for license (nee licence,
copyright, legal, copying etc.) files to be discovered and made available
from the snap metadata by installers, the snap store or other consumers.
Which is what we are really asking.
--
Stuart Bishop <stuart.bis...@canonical.co
On 2 September 2016 at 15:01, Stuart Bishop <stuart.bis...@canonical.com>
wrote:
>
>
> On 2 September 2016 at 00:46, Leo Arias <leo.ar...@canonical.com> wrote:
>
>> This is a pain point for me too. Most upstreams store the version number
>> in only one
; that.
>
> We could make that snapcraft --snap-version=$(git rev-parse HEAD) just
> overwrites the version field, useful immediately for people not using
> launchpad.
>
> pura vida
>
>
>
--
Stuart Bishop <stuart.bis...@canonical.com>
--
Snapcraft mailing li
18 matches
Mail list logo
