Hello!
How do you choose which programs will be included in the Lubuntu Live / Installed version?
And how do you suggest options?
The installer has three options: minimum, typical (recommended) and one including other stuff.
The typical usually has what you need (office, graphics, other utilities). If you need more, it’s normally special stuff that needs to be added separtely anyway.
1 Like
I’ll respond here, but as I don’t understand what you’re really after, and @ne29914 may have already provided your answer, I may give little useful anyway.
If I want to know what exists on an ISO, which of course applies to your live question, I look at the manifest file to see what packages are on the ISO… For the recently released Lubuntu 25.10 that will be https://cdimage.ubuntu.com/lubuntu/releases/25.10/release/lubuntu-25.10-desktop-amd64.manifest
Of course, an installed image will vary to that; for starters the installer we use calamares will appear in that list; but its no good on an already installed system so it’s an example of something that won’t exist on an installed system.
Further as @ne29914 highlighted; you can install only a subset of those files (minimal install option), OR choose to install options that are NOT found on the ISO but downloaded during the installation so those won’t be on the list as well.
When reading that manifest file; the deb packages are listed first; snap packages get listed at the bottom (a minimal install gets no snap packages installed anyway, but the snapd infrastructure listed in the deb section are also not installed anyway).
Of course that list is package specific, and whilst most can be easily worked out, eg. the line
featherpad 1.6.2-0ubuntu1
applies to the featherpad text editor, not all app names and package-names are that easy. How familiar you are with open-source software will be greatly in play here, but you may find our bug page handy, ie. https://git.lubuntu.me/lubuntu-wiki/wiki/wiki/Bugs as it include a table with ‘component’ that maybe easier; it also contrasts the historical LXDE to the modern LXQt; but note some of those apps listed aren’t included any more (eg. email client hasn’t been provided for some time)
When installing apps; I just consider this Lubuntu system as a Ubuntu one anyway; I’m just choosing to use the LXQt desktop (by the Lubuntu team) on my Ubuntu questing (25.10) box.
FYI: If you’ve not yet installed, and are wondering which option to install; if it’s an install I’ll use I always opt for the Normal install, using the others only in Quality Assurance testing.
1 Like
I think this is more of a meta-question than that. I think it could be phrased as:
How are packages chosen by the developers for inclusion?
and
How does one suggest packages for inclusion?
3 Likes
Exactly.
Bad English is due to use and translator.
1 Like
Discussions take place between Lubuntu team members (and other contributors), mostly in public rooms (matrix etc), but some can be in rooms that are accessible only to Lubuntu members. If the old Lubuntu Discourse was still in operation, I could provide a link to the removal of certain packages such as an example I used in my prior reply (ie. email client), but that site is gone, and we’ve not had any such discussions on this site (we could ask for feedback or opinions from end-users before the change actually occurs).
How a discussion gets started tends to vary; it could be a suggestion made to Lubuntu via mailing list (historically anyway; these lists are being phased out), on IRC (again historical example), on matrix, on sites such as this discourse (we received quite a few on the older Lubuntu discourse), a bug request (worded as a ‘feature request’ so its clear its not a bug report against current, but request for change) or even social media comments (I could see for example a reddit post that could start a discussion by example). Do note where requests are made officially (bug report for example allows for tracking) there is a far higher chance of discussion occurring, than say a post on reddit or other social media site.
Changes require team resources to exist to implement (ie. developer availability), otherwise it may just get treated as a wishlist item, and pushed for a future release. Changes are almost always made only to the future or development release (ie. resolute) and not stable or released products
1 Like