Remote repository cleanup #3
ihatethefrench
started this conversation in
General
Replies: 3 comments 3 replies
-
Anything flutter or jade_gui related can be removed as they're not used anymore. |
Beta Was this translation helpful? Give feedback.
0 replies
-
My suggestion for [repositories]
repos = [
"crs:crystal-keyring",
"crs:onyx",
"crs:wallpapers",
"pkg:base",
"pkg:crystal-dev",
"pkg:crystal-grub-theme",
"pkg:filesystem",
"pkg:gnome-apps-meta",
"pkg:lsb-release",
"pkg:neofetch",
"pkg:pfetch",
"pkg:pkg-warner",
"aur:chrome-gnome-shell",
"aur:ckbcomp",
"aur:iso-flag-png",
"aur:mkinitcpio-openswap",
"aur:python-xdg",
"aur:timeshift",
"aur:timeshift-autosnap",
]
[repositories.urls]
crs = "https://github.com/crystal-linux/{}"
pkg = "https://github.com/crystal-linux/pkgbuild.{}"
aur = "https://aur.archlinux.org/{}" |
Beta Was this translation helpful? Give feedback.
3 replies
-
And for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, we have many potentially redundant packages that we build for our repositories. I believe it'd be good practice to sift through these and make sure we're only building what we actually need.
Here are some of the packages we're building for our
any
repository, for example:As well as our
x86_64
repository:Just looking through these, I can immediately see some packages we simply do not ship, need to ship or maintain any more (e.g.,
lapis
,citrine
,flutter
, etc.)Which ones should we keep and which ones should we remove?
Beta Was this translation helpful? Give feedback.
All reactions