| 20 May 2021 |
 _hc | proletarius101: I think a) you should try stripping out as many of the pre-installed packages as possible. b) leave backports setup, but default to the buster packages | 17:19:11 |
| _hc | I think it will have to use stretch's openjdk-8 packages rather than buster's 11 | 17:19:39 |
| _hc | packages that need 11 could install it in sudo: | 17:20:02 |
 proletarius101 | In reply to @eighthave:matrix.org
proletarius101: I think a) you should try stripping out as many of the pre-installed packages as possible. b) leave backports setup, but default to the buster packages How can I know which are required? Actually it's supposed to only install fdroidserver's dependencies, isn't it? | 17:20:50 |
| _hc | yeah, I think that would be a great place to start | 17:21:15 |
| proletarius101 | which is apt-get build-dep | 17:21:38 |
| _hc | you can do apt-get install fdroidserver/buster-backports then apt-get purge fdroidserver to get only the Depends: | 17:21:49 |
| _hc | build-dep won't be everything, since that's just what is needed to build the package | 17:22:06 |
| proletarius101 | * which is apt-get build-dep fdroidserver | 17:22:07 |
| proletarius101 | In reply to @eighthave:matrix.org
build-dep won't be everything, since that's just what is needed to build the package right | 17:22:19 |
| proletarius101 | That would miss some build packages, which was assumed to be pre-installed. e.g. cmake | 17:24:24 |
| proletarius101 | should they be added? | 17:24:28 |
| proletarius101 | or should they be rather installed by the sudo: | 17:25:08 |
| proletarius101 | * That would miss some build packages, which were assumed to be pre-installed. e.g. cmake | 17:25:35 |
| proletarius101 | IMO they should be installed by sudo:, since not all apps need them | 17:26:36 |
|  djBRDF left the room. | 17:26:58 |
| proletarius101 | Then that would trigger some errors, which should be solved one by one | 17:27:57 |
| proletarius101 | Or I try to leave them as-is. Hard to identify, though | 17:28:32 |
| djBRDF joined the room. | 17:28:57 |
 jochensp | I vote for making dependencies explicit through sudo | 17:30:05 |
| _hc | I totally agree with jochensp | 17:33:27 |
| _hc | I see it like gitlab-ci: use a minimal base image, then the rest of the requirements are specified explicitly | 17:34:13 |
| _hc | I believe nixOS is like that too | 17:34:25 |
| _hc | that's how a Debian package works as well | 17:35:42 |
 cdesai | instead of sudo it could be 'apt ' | 17:36:08 |
| _hc | this approach would also make it easier to try other base images, like nixOS could be interesting. | 17:37:58 |
| _hc | like proletarius101 said, there will be errors. so just a trial run with a super minimal base image will let us understand how feasible the idea is | 17:38:48 |
 Fay (she/her) | In reply to @eighthave:matrix.org
幸猫: I think the main thing is for someone to take ownership of some of those boxes I don't mind doing that. but there's a lot I don't know, like:
- what's (supposed to be) on there now
- what's expected of me
- who's responsible for decision making
- what happens when I'm not available or something "goes wrong"
- how we handle access rights, updates, reboots, monitoring, communication, documentation
| 17:40:57 |
| Fay (she/her) | * I don't mind doing that. but there's a lot I don't know, like:
* what's (supposed to be) on there now
* what's expected of me
* who's responsible for decision making
* what happens when I'm not available or something "goes wrong"
* how we handle access rights, updates, reboots, monitoring, communication, documentation | 17:41:36 |
| djBRDF left the room. | 17:41:54 |
