> If you tell us what you want to package, we can tell you a good example > out of more than 50.000 packages
I'm really looking for generic examples. My motivation is using a standard, widespread convention or otherwise popular tooling for deploying software (which - at work - is not open source). So that new developers don't need to learn "the process". When you see a "debian" folder in a repository you probably already guess that the project will build a .deb package. When you see a .deb package you can easily guess how it will be installed. One of the softwares is a Java Web application (delivered to us as a .jar and some accompanying files) that is deployed into a JBoss application server preinstalled on the host. The other is actually not even Java software, it's a bunch of shell scripts and two Python CLI applications that are installed from an internal PyPI index. So, it's all about copying files somewhere and performing installation activities that are encapsulated in the .deb file. > > location where it has write access. The scenario is, I have users that > > must install the software on a managed machine. The system > > administrators manage the operating system as such, the users install > > and run their software in user space. > > As far as I know NO WAY to do so. Let me mention that for my use case it's sufficient that we assume there are no dependencies, or that if we have unresolved dependencies (e.g. most notably a JRE) the installation process aborts brutally. Doing some research I found a few interesting discussions: - https://askubuntu.com/questions/339/how-can-i-install-a-package-without-root-access - https://askubuntu.com/questions/193695/installing-packages-into-local-directory The two suggested solutions are using `--force-not-root` or simply unpacking the .deb archive file: dpkg -i --force-not-root --root=$HOME package.deb ar p package.deb data.tar.xz | tar xJv --strip-components=2 -f - The latter will certainly not run pre- or post-install scripts, which is one of the reasons I want to do the packaging, though. (Encapsulate the installation logic in the installation package itself!) Now I would need a simple packaging setup to verify that those commands actually work for my use case. Peter
