Hello Hibby, On 28/10/2024 12:42, Dave Hibberd wrote:
Let's start with content and then reproduciblity can follow once things are moving.The primary use case I have in my head is for an amateur 'shack PC' used at a one day event or in a shared-use environment. Typically, this will be an old machine belonging to a club member or the person running. They will likely be looking to keep logs, use datamodes and perform a few other tasks. On Friday, 25 October 2024 09:17:32 GMT Roland Clobus wrote:On 19/10/2024 12:43, Hibby wrote: Regarding the content of the live image: * I see that there are many metapackages [R2], do you want all of them (with 'hamradio-all') to be installed?This feels like it would be overkill - there are a number of packages buried away which are typically reserved for 'infrastructure' type projects and don't suit the more temporary nature of a live image - it's not worth installing the 'svxlink' [1] set of packages in every install for the amount it's actually going to be used, for example. I think there's a couple of metapackages where everything will be useful, and a couple where a more measured approach of just one or two packages will be suitable.* Do you also propose to override some default values for some packages?There are a few where autostarting the service might not be appropriate, but I'd need to identify which ones!* Which desktop environment would you recommend to your users? If possible, I would suggest to offer only one, and not all DEs (e.g. either GNOME, KDE or a lightweight variant)Given the nature of most 'ham shack' PCs is someone's old computer, something lightweight would be good - my running preference in experiments so far is lxqt. [1] https://packages.debian.org/source/sid/svxlink
You can find an initial configuration for the blend at [2].I've excluded the installers and i18n packages to make the image smaller, it is 'only' 2.4GB instead of 3.6GB.
Feel free to experiment with the package list as you see fit.See the generic instructions on [4]. Note that I strongly suggest to use a proxy, since downloading several GB in packages for every attempted build is no fun at 300 baud (wink :-)
After running 'rebuild.sh --configuration hamradio --debian-version sid' on the checked out git branch, you can for subsequent builds use 'lb clean --purge;lb config;lb build' (which means that you can tweak the config directory more easily than by patching rebuild.sh for each attempt). Running 'rebuild.sh' clears your carefully constructed configuration directory.
The live-build manual [5] can also be a good help (even though some parts are somewhat out-of-date)
Should I add the hamradio mailing list for further discussions, and if so, where is it? The Hamradio Blend Support page points to a removed list (pkg-hamradio-user) [3]
With kind regards, Roland Clobus [2] https://salsa.debian.org/live-team/live-build/-/merge_requests/375 [3] https://www.debian.org/blends/hamradio/support [4] https://wiki.debian.org/ReproducibleInstalls/LiveImages[5] https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html
OpenPGP_signature.asc
Description: OpenPGP digital signature
