From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2316 Path: news.gmane.org!.POSTED!not-for-mail From: Thomas Caravia Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?) Date: Mon, 15 Jan 2018 13:53:41 +0100 Message-ID: <20180115135320.43c0dd84@kadisius> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1516020720 31990 195.159.176.226 (15 Jan 2018 12:52:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 15 Jan 2018 12:52:00 +0000 (UTC) Cc: Jonathan de Boyne Pollard To: Supervision Original-X-From: supervision-return-1907-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Jan 15 13:51:56 2018 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1eb4Es-0007Nm-06 for gcsg-supervision@m.gmane.org; Mon, 15 Jan 2018 13:51:46 +0100 Original-Received: (qmail 7910 invoked by uid 89); 15 Jan 2018 12:54:16 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 7903 invoked from network); 15 Jan 2018 12:54:16 -0000 X-Originating-IP: 88.190.98.63 In-Reply-To: Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2316 Archived-At: Hello, > > Do you know whether anyone has documented how to build on a non-Debian > > linux? An rpm spec file would be ideal, but just simple non-Debian > > centric build instructions would be better than nothing. > > Thomas Caravia constructed the Archnosh PKGBUILD the same way. It does > the slashpackage-style build, then takes the built slashpackage-style > package and parcels it out into a set of Arch binary packages, with a > light dusting of patches to a handful of service bundles. It even > mostly re-uses the Debian maintenance scripts. I'm not familiar with rpm but my packaging is just this: 1) package/compile: you'll need "redo" to build 2) package/stage: you can tweak this script to fit your distribution's filesystem hierarchy 3) use the resulting package trees for your packaging: in my case one-for-one copying 4) include install/upgrade/remove scripts from package/debian for the packages that need them Service bundle patches account for differences in paths or usernames with Archlinux, when I find them. > (On that note, Thomas: You may enjoy the start that I have made in 1.37 > to a _Packages and Ports_ chapter in the /nosh Guide/. Yes, I currenly > plan for the |.p|/|.func| system to get at least a short mention.) It did not go unnoticed! Regards, Thomas