>> There is a way around that, but it’s rather counter-intuitive and
>> error-prone: add the packages containing those libs to the list of
>> stage-packages, then explicitly exclude them from the resulting snap
>> using the prime/snap keyword. You won’t be able to exclude them if you
>> didn’t include them through the stage packages first.
>
> Isn't this what Kyle fixed by adding build-attributes: [no-system-libraries] ?
>
> http://snapcraft.io/docs/build-snaps/syntax#parts
Yes, that seems to be it, indeed. Thanks for the pointer Leo, I wasn’t
aware of this new feature. With this, no need to artificially add
stage packages. Neat!
Also
>> There is a way around that, but it’s rather counter-intuitive and libraries] ? snapcraft. io/docs/ build-snaps/ syntax# parts
>> error-prone: add the packages containing those libs to the list of
>> stage-packages, then explicitly exclude them from the resulting snap
>> using the prime/snap keyword. You won’t be able to exclude them if you
>> didn’t include them through the stage packages first.
>
> Isn't this what Kyle fixed by adding build-attributes: [no-system-
>
> http://
Yes, that seems to be it, indeed. Thanks for the pointer Leo, I wasn’t
aware of this new feature. With this, no need to artificially add
stage packages. Neat!