<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=8016&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Which tool is best for Devuan Derivative-making?]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=8016</link>
		<description><![CDATA[The most recent posts in Which tool is best for Devuan Derivative-making?.]]></description>
		<lastBuildDate>Tue, 02 Jun 2026 15:26:59 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Which tool is best for Devuan Derivative-making?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64085#p64085</link>
			<description><![CDATA[<p>I haven&#039;t used live-build in over 10 years and never on devuan. I know there are some people who have used it with devuan. <br />Devuan live-sdk is similar to live-build in that it pulls packages from the repo and builds the system in a chroot. This is good if you&#039;re making a lot of different isos - you just need to alter the configs to do a different build. The downside is that you often don&#039;t know the build failed until the end of the run, then you have to start over. When you start building a new release, you can have frequent failures in the beginning because some packages in your list might not be in the repo anymore or may have changed names.</p><p>refractasnapshot does not require access to the repo to build the iso. It makes a copy of your running system with a few things excluded and puts that into the iso. Since it&#039;s copying an installed system, any questions about missing packages have already been answered before you started to make the iso. Also, since it&#039;s copying the running system, any changes you make right before running it will be copied into the iso. The downside of this method is that you must have an installed system, either on hardware or in a virtual machine, for each flavor you want to build.</p><p>To adjust what gets copied by refractasnapshot, edit /usr/lib/refractasnapshot/snapshot_exclude.list. See &#039;man rsync&#039; for details.</p><p>Edit: one more difference between live-build or live-sdk and refractasnapshot is that refractasnapshot builds an iso that has an unprivileged user with a home directory. The others do not, but the live-config scripts create the user and home when the system boots. This affects which live-config options are used in the boot command. See &#039;man live-config&#039; and probably &#039;man live-boot&#039; too.<br />Note that live-build, live-sdk and refractasnapshot all use the debian live-boot and live-config scripts.</p><p>I don&#039;t know what those others are.</p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Tue, 02 Jun 2026 15:26:59 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64085#p64085</guid>
		</item>
		<item>
			<title><![CDATA[Which tool is best for Devuan Derivative-making?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64082#p64082</link>
			<description><![CDATA[<p>There are many tools you can use to make your own Devuan Derivative:<br />- live-build<br />- devuan-sdk<br />- penguins&#039; eggs<br />- oa tools<br />- Refracta<br />Does anyone know which one is the best?</p><p>Additionally, I&#039;ve heard that Refracta also saves user data (/home/user/), is there any way to mitigate this?</p>]]></description>
			<author><![CDATA[dummy@example.com (lhanhs)]]></author>
			<pubDate>Tue, 02 Jun 2026 03:49:39 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64082#p64082</guid>
		</item>
	</channel>
</rss>
