Hi,
while thinking about what I could experiment with snapping next I checked
what I still use some external repositories for - as I considered those a
great list of opportunities.
One that I found there was my printer driver which consists of these
packages [1] provided by [2].
But thinking about
On Thu, 2016-08-04 at 11:21 +1000, Jacob Zimmermann wrote:
> >
> 2) Assuming that it was necessary to patch hatari like Jamie suggested,
> what is the idiomatic way to apply a patch to upstream sources before
> compiling?
>
Once this bug is implemented, patching for something like shm_open() wou
Devs, thanks for your help.
My contribution
$ snap find vs
Name Version Developer Notes Summary
deadbeef-vs 0.7.2-snap1 vs - The Ultimate Music Player
languagetool 3.4-snap2vs - LanguageTool
osddm 4.1.3.901-snap1 vs -
Le 04/08/2016 à 15:53, Vasilisc a écrit :
> Devs, thanks for your help.
> My contribution
>
> $ snap find vs
> Name Version Developer Notes Summary
> deadbeef-vs 0.7.2-snap1 vs - The Ultimate Music
> Player
> languagetool 3.4-snap2vs - L
I have created a ntopng snap for the dev branch of ntopng. The snap works
in strict mode once you connect it to the network-control interface. I
currently registered the snap as ntopng-blake as ntopng is a reserved name.
Let me know what you think.
sudo snap install ntopng-blake
sudo snap connect
Can someone describe the strategy or point me to an example for including a
custom kernel driver as part of a snap?
I'm trying to put together a snap that requires several custom kernel
drivers be installed along with the snap and would like to know the
"snappy" way of doing this.
Thanks, Mike
--
Le 04/08/2016 à 17:40, Blake Rouse a écrit :
> I have created a ntopng snap for the dev branch of ntopng. The snap
> works in strict mode once you connect it to the network-control
> interface. I currently registered the snap as ntopng-blake as ntopng
> is a reserved name. Let me know what you thin
