Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Peter Bittner Newsgroups: linux.debian.maint.java Subject: Re: Debian package examples for Java software Date: Sat, 14 Sep 2024 21:30:01 +0200 Message-ID: References: X-Original-To: debian-java@lists.debian.org X-Mailbox-Line: From debian-java-request@lists.debian.org Sat Sep 14 19:26:33 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.787 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, FVGT_m_MULTI_ODD=0.02, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmx. - helo: .mout.gmx. - helo-domain: .gmx.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Ui-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a X-Gm-Message-State: AOJu0YwGFe3IiSZ7mZ/EnrO4XhMBkoCGuk8IG9G8nFpQ9RjCz0TzoA26 C7DZHHl+hEfxQouKZj/xdhqm4Y6Siv45orM7SoFigJ8Se/zwCMMwvV2BeoU6IpBh7+5bYuCqXGc sPLaJ0L2j1sYU14LEq9JXv5+1EJBtftOB+E5C X-Google-SMTP-Source: AGHT+IFjXZJlI3owraoYp8eylgLKvj250cOl1xLsbMJyLy+w2Hg2fJBBhnEvWjRRyi24vUlzz7yXtwyLHYVOZEU2n5w= X-Received: by 2002:a05:690c:448a:b0:6d0:f91e:2ff0 with SMTP id 00721157ae682-6dbb6b12e95mr73299287b3.11.1726341974428; Sat, 14 Sep 2024 12:26:14 -0700 (PDT) MIME-Version: 1.0 X-Gmail-Original-Message-ID: Content-Type: text/plain; charset="UTF-8" X-Provags-ID: V03:K1:p2b3n72uX/D9V3u+6fxIBZcz99csRKsfFOySMzVavoLyFja6XAX hhEdn0JQOTvNSdvUJArMWJ4tkSnX0tzrQurTrVZOoIPZ1AGLk5XXKt+pd62DT1Q9IFItdZF LsUJM7RsG9BmipwILrWmHc5Q9g9Q8DPnMtEohCEWkQOw9eRdfR1Y+ljFOYouXsQEmEmSjXR HgVfG63jKrlAIOXdCcXfQ== Ui-Outboundreport: notjunk:1;M01:P0:IM3KgoEFo+o=;aCTvKOulxqJAfsrUZOsuDqfCwTA BbYwJlRTKBxzoP90lEM0pnwofGfNTehJvumP7rV6yMk8kKSdcqonxN3JIM4X8ilGrG13nzX5Q ais1+55w4JWYeKO0LsupOC/uNhMJFHgZTBGcRzTXzvt35dFq76uY76hzGCKwc6hVPESHsnA/F GgG88sncyOfo3LT+YvCjZlcE/C/Q2qYGCBYDDD5i1yomhAn74Ur4S4b4Kq5c6zcYfFlcJt+Lg Xsrokt+mC4b79c1bJ/dqk7oVRSjcomNY0ZFpJkskzS2k0wH5Z5soR5JDw3CmKwIElI8ypAhGU kE5QvVyHoL9dLWQM8OwB5vEnQvJcaVOTilY/NiDU45AVridXPV1S45eItO2jrvPh6OF7+q+/c bGZiOIK0vqlRu+wUt+Bpt/rz1eXZHzr5H/4enFaVhqZ72r0aIXRujwWAv+dq9+qHElyCFTIFQ 0CdhN4KsSUaZqmrJ53nGPyki2T+3CvyLWUB1CLoOYmsGc7+eVHFeF9+BFNwdZkGU8w9fz4JSy 3bYmJn9bIa5hGbcCiHfRTZ9UexjBGAnuIvYVsCAfvD0Ct9eib0tAvFTTX09a1Sjwn2eVrTNpJ 9ObufD6p+C3Ta1UCDC335k+1gAJd3ClDcf88xezDi8ghIsgPWh8gcQ8q36abOecrB42AsFXNB JLaejhcL0CEpyupwiVjDN3Tz8jOH6QoU23RnJ6S0mSa3miVO41odeerjaldXx8KaRDtxnwDut NHVDqs9+V8cdK8FFCPlHzbDGZyioneUTWRdAP4CiCYJgD+yysmNG3L5qfGTnh37zbhsxh7x5k IlEM1RoXM9F9wcS2x20/WEqZJsJXTHZKZd4FiZG9eO5SY= X-Mailing-List: archive/latest/23501 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAHywH5D4wA4u47jDH6qwMvnMhnF+c3Tb+_2G5b7NXnsEnoZ4tw@mail.gmail.com Approved: robomod@news.nic.it Lines: 48 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 14 Sep 2024 21:25:48 +0200 X-Original-Message-ID: X-Original-References: <8b94e20f-2d6d-4297-814b-9e4e18febb69@debian.org> Xref: csiph.com linux.debian.maint.java:12803 > 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