This should probably be enough for an "in-house distro".
--The GPL does not consider making and using multiple copies in one organization or company as "distribution" And --MPL also has similar view --Refer to Q6 of FAQ -Ubuntu IP Policy is almost the same. - You can modify Ubuntu for personal or internal use - You can make changes to Ubuntu for your own personal use or for your organisation’s own internal use.
When "distributed" outside the organization, at least the following measures should be taken in accordance with the GPL, MPL, and Ubuntu IP policies.
--Prepare a system to distribute the source code
Fully devoted to telework / remote work, which is attracting attention as a countermeasure against COVID-19
--Based on xubuntu 20.04 (lubuntu 20.04 has not been released at the time of creation) --All Network Manager VPN plugins included --All Remmina's additional protocol plugins are included --Leave the browser --For other packages, "Erase what can be erased"
--When you burn a copy of the distro to a USB memory and hand it over in-house, each person can hand it over with different "VPN and remmina connection settings" (unsolved) ――The writer belongs to the "department that can't be helped unless you go to the place where the equipment and the actual item are", but people in the indirect department are also going to work as usual. (Probably the environment is undeveloped?)
I didn't make it for external distribution this time, but to get the source code of the package, look at the manifest file and make it in the form of * package name = version *
$cat /media/cdrom/casper/filesystem.manifest |sed -e 's/ /=/g' >package.list
Anyway, it's good. However, if you try to feed all packages with apt source --download-only
NOTICE: 'accountsservice' packaging is maintained in the 'Git' version control system at: https://anonscm.debian.org/git/collab-maint/accountsservice.git Please use: git clone https://anonscm.debian.org/git/collab-maint/accountsservice.git to retrieve the latest (possibly unreleased) updates to the package. (Omitted below)
I was told,
$cat /media/cdrom/casper/filesystem.manifest |sed -e 's/ /=/g' | sed -e 's/^/apt source --download-only /g' >pkg-dl.sh $chmod u+x pkgdl.sh
It seems that it should be done.
--Batch acquisition of package source code with ~~ apt etc. ~~ ――I can't think of a good way to automate the creation of ISO images with different settings for each person. --In the case of external distribution, it may take some time to drop the source code of the Snap package (delete it if unnecessary)
-** I missed the opportunity because I came up with the material late ** --The requirement definition was loose --In the first place, if it's your own (because the number is small and each has different uses), "a meta package that installs only the things you want to put in common to all machines" is enough