Details
- Reviewers
- None
- Commits
- rG2006e3634b40: Modernize DVD package set in preparation for 14.1
rGa926bf9254b2: Modernize DVD package set in preparation for 14.1
rG8f7da18ea248: Modernize DVD package set in preparation for 14.1
rG0543cdc36ac6: Modernize DVD package set in preparation for 14.1
rGd31ed58b9f93: Modernize DVD package set in preparation for 14.1
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Throwing this out for developers and the community to provide feedback on.
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 14–15 | Do we still need this? We now have /usr/bin/unzip. | |
| 15 | Is this the appropriate linux base port to include, or should we be pointing users at a different (newer?) one? | |
| 18 | Are these the right drm-kmod packages for 14.1? | |
| 34–35 | Should we add wayland and any related packages? | |
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 14–15 | IMHO, perhaps git-lite or even git-tiny would be more suitable? | |
FYI, at $WORK the only packages we include in the DVD image are:
- ports-mgmt/pkg
- sysutils/py-salt , because Salt can install everything else
- net-mgmt/lldpd, which helps us debug network problems that would prevent Salt from working.
For desktop use, I really don't think that the packages on the DVD are very important. We can't possibly put every package on the DVD, or even the most popular packages. So what's the point of having any? Just to reduce users' download times?
Speaking of py-salt: It will also pull in python that also could be benefical for ansible.
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 30–31 | x11-drivers/x86-video-intel? (maybe VESA is good enough for the DVD?) x11-drivers/x86-input-vmmouse (since we have the vmware video driver?) | |
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 30–31 | This would make sense in the context of VMware. Besides this: how can we figure out how much space (and therefore ports) we can safely provide? | |
It's probably worth to consider porting nuage-init from 15-CURRENT (where it's in base) to 14.1.
Besides this: how can we figure out how much space (and therefore ports) we can safely provide?
This is a good question - how much space do the current packages require? Do we need to remove packages to hit a size target, or is it just about utility and general housekeeping?
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 14–15 | Looks like it was originally added in 042a51f641253 but doesn't indicate a specific reason. /usr/bin/unzip is probably sufficient and we could remove this. | |
| 15 | I think it's old enough to be not particularly useful and we could remove it even without a replacement. | |
| 34–35 | I'd say so | |
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 34–35 | This is a good example of why the ports statistics from bsdstats.org were so useful. Too bad that site is dead. Even its replacement bsd-hardware.info is dead too. | |
So silly question: what are we trying to solve with these packages in first place?
Historic value to have a copy of the packages saved before they disappear?
Give users a graphical desktop (unlikely with this list)?
Because we always did?
...?
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 18 | And if we include the packages, can we also include the firmware as otherwise they are as good as the network people are attached to? | |
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 18 | Bjoern, which firmware packages should we include? Network devices seem the most important. fwiw, I use drm-510-kmod. | |
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 34–35 | Anyone know which wayland and related packages to include? | |
| release/scripts/pkg-stage.sh | ||
|---|---|---|
| 18 | I would add net/wifi-firmware-rtw88-kmod as that driver is working and connected and has no more firmware in base. Would at least help after the installer (after reboot) to get connectivity. | |
To "So what's the point of having any?". Having these packages available provides a means for enthusiastic/inquisitive users the tools to find, access and build applications.
- firefox - to find (though something with much less complexity would be sufficient and remove the need for window managers)
- git@lite or tiny - to pull down (or rsync)
- pkg - to assemble packages for installation
- portmaster - to build dependencies nicely and perform maintenance (or include poudriere)
Some of the other tools provide convenience for doing the above. However if the objective is to direct users to binary packages then only pkg is necessary.
The goal of the packages on the DVD is "give people enough packages to get a desktop up and running". They'll almost certainly want to use pkg(8) to install more packages later (maybe Chromium, maybe Thunderbird, maybe Libreoffice...) but we can't include everything and this at least provides a decent starting point.