Hot answers tagged

7

If you do need a reboot after installation you will make a call to /usr/share/update-notifier/notify-reboot-required in the .postinst script for your package. This can easily be found be reading the .postinst script of any linux-image package. However, I would be concerned about any custom PPA that requires a reboot after installation. Other than ...


5

Yes, there is a real need. There has been a real need for something like this since the first time one software depended on another. Let's make this clear: Managing dependencies is hard. There's a reason why it's called dependency hell. Packaging systems like RPM and Debian were created with the intent of avoiding dependency hell. However, somebody must ...


4

In the case of python you probably want some of those build-packages to be stage-packages. The python plugin sets PYTHONPATH to be within the snap which is why it's missing these packages (you have them installed on the host system instead). Byt the way, if this upstream had a proper install_requires in setup.py these dependencies would have been taken care ...


3

Building a package.deb from directories : cd new-folder/ && mkdir -p packagename/DEBIAN Your files e.g. usr/local/bin/executable goes into packagename/ ... and the file control into DEBIAN/ Example control file : Package: name Version: 1.1-1 Section: base Priority: optional Architecture: amd64 Depends: Maintainer: Jerry Donut <jerry@donut....


2

You are missing: A .desktop file to be installed in /usr/share/applications/ for Dash/App Menu listing/launching. An icon to be installed in /usr/share/icons/ for this .desktop launcher. Another little bit different .desktop file to be installed in /etc/xdg/autostart/ for session autostart. XD I will not give you examples! You know why? Update to fix ...


2

You need to white-list (if you are set it to use the main server): http://ubuntu.com https://ubuntu.com and if you plan on using the canonical repository as well those: http://canonical.com https://canonical.com


2

We don't treat language specific case with snapcraft but rather build system. You surely are using a build system with your package, this one being autotools, make, cmake, qmake… Snapcraft have plugins for those, and you can find demos for each plugins in the snapcraft source tree (or installing snapcraft-examples). If you look at snapcraft.io tour, the ...


2

Take a look at https://github.com/ubuntu/snappy-playpen/blob/fd5d4a3a1e3f0acc13370adbf98c9a3481d1328a/leafpad/snapcraft.yaml for a simple example. The relevant part of snapcraft.yaml here is: parts: leafpad: plugin: nil stage-packages: [leafpad] Here you define a part called leafpad, for which nothing needs to be done (nil plugin), but the ...


1

You're running into part of the security structure, which even in configure: devmode still prevents the snap from doing arbitrary operations on the system. I've been fooling around on the snappy-playpen github, (which has a gitter chatroom), but I am by no means an expert. If you are defining plugs for each of your apps/parts and are hooking them up to the ...


1

In a snap package, you can simply have two parts: one being your Qt app, the second one being the python script. Parts in snaps are handled by plugins and they make sure everything gets installed in the right place and have what they need. For example could your Qt app be built using the cmake plugin and your python script using the python3 plugin. In short:...


1

You can't use pbuilder-style hooks, no. However, generating locales doesn't require root in principle; it's just the default locale-gen arrangements that write to the system locale directories and therefore require root. You could instead use localedef to generate the locales somewhere under your build directory and point your test process at that using ...



Only top voted, non community-wiki answers of a minimum length are eligible