Use sources.list.d folder instead of appending to sources.list for apt repository #34

Closed
opened 2025-09-10 22:50:00 -05:00 by giteasync · 5 comments
Owner

Originally created by @mtrp12 on GitHub.

In the vscodium website, the install command for ubuntu/debian adds the deb repo of vscodium to the sources.list. It would be better to use vscodium.list under /etc/sources.list.d as it would enable cleaner management of the repo. Adding to sources.list clutters the sources.list unnecessarily. It would be great if you changed it, as many people including me just copy paste the commands. Thank you.

Originally created by @mtrp12 on GitHub. In the vscodium website, the install command for ubuntu/debian adds the deb repo of vscodium to the sources.list. It would be better to use vscodium.list under /etc/sources.list.d as it would enable cleaner management of the repo. Adding to sources.list clutters the sources.list unnecessarily. It would be great if you changed it, as many people including me just copy paste the commands. Thank you.
Author
Owner

@paulcarroty commented on GitHub:

@stripedpajamas it just split the one configuration to many small /etc/apt/sources.list.d/{app1.list,app2.list...} files. The docs says:

The package resource list is used to locate archives of the package distribution system in use on the system. This control file is located in /etc/apt/sources.list and *additionally* any files ending with ".list" in /etc/apt/sources.list.d are included.

My opinion - this is just a waste of time because apt will use this sources in the same way.

@paulcarroty commented on GitHub: @stripedpajamas it just split the one configuration to many small `/etc/apt/sources.list.d/{app1.list,app2.list...}` files. The [docs](https://linux.die.net/man/5/sources.list) says: `The package resource list is used to locate archives of the package distribution system in use on the system. This control file is located in /etc/apt/sources.list and *additionally* any files ending with ".list" in /etc/apt/sources.list.d are included.` My opinion - this is just a waste of time because apt will use this sources in the same way.
Author
Owner

@PalinuroSec commented on GitHub:

to put the repo in /etc/apt/sources.list.d/ is a good idea, but the pull request changes the wrong files: the build results of the jekyll build process.

let me pull the changes and move them to the proper files

@PalinuroSec commented on GitHub: to put the repo in /etc/apt/sources.list.d/ is a good idea, but the pull request changes the wrong files: the build results of the jekyll build process. let me pull the changes and move them to the proper files
Author
Owner

@PalinuroSec commented on GitHub:

website updated and readme file created to make the development and testing process easier

@PalinuroSec commented on GitHub: website updated and readme file created to make the development and testing process easier
Author
Owner

@optikfluffel commented on GitHub:

@mtrp12 feel free to open a PR over at VSCodium/vscodium.github.io

@optikfluffel commented on GitHub: @mtrp12 feel free to open a PR over at [VSCodium/vscodium.github.io](https://github.com/VSCodium/vscodium.github.io)
Author
Owner

@stripedpajamas commented on GitHub:

@paulcarroty I don't have enough context to know if this makes sense to do -- can you weigh in here?

@stripedpajamas commented on GitHub: @paulcarroty I don't have enough context to know if this makes sense to do -- can you weigh in here?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: VSCodium/vscodium.github.io#34