Blacklist/skip precompiled packages #56

New Issue

Open

opened 2021-11-14 02:11:27 +01:00 by alissonlauffer · 4 comments

alissonlauffer commented

2021-11-14 02:11:27 +01:00

Now that the repo allows the creation of new mirrors, we could also blacklist packages that are not compiled and are just repackaged from an already built binary (for example: vivaldi and cuda), thus saving extra space (especially since just cuda and cuda-tools together are taking up about 2 GB of space :P).

Could this also be done automatically by comparing whether the package contents are the same as in upstream package?

Now that the repo allows the creation of new mirrors, we could also blacklist packages that are not compiled and are just repackaged from an already built binary (for example: `vivaldi` and `cuda`), thus saving extra space (especially since just `cuda` and `cuda-tools` together are taking up about 2 GB of space :P). Could this also be done automatically by comparing whether the package contents are the same as in upstream package?

titaniumtown commented

2021-11-14 02:13:22 +01:00

Yea, I noticed that too. Completely unneccisary to have precompiled packages in this repo lol.

Gontier-Julien commented

2021-11-14 02:28:34 +01:00

Never noticed that haha
But how many are they? Because it going to be a manual thing to do

Never noticed that haha But how many are they? Because it going to be a manual thing to do

anonfunc added the

enhancement

label 2021-11-14 12:14:57 +01:00

anonfunc commented

2021-11-14 13:09:13 +01:00

Owner

I would suggest removing the really big ones (cuda for example). Removing all might be a very time consuming task, especially if you remember this list is subject to change based on upstream arch decisions.

I would suggest removing the really big ones (`cuda` for example). Removing all might be a very time consuming task, especially if you remember this list is subject to change based on upstream arch decisions.

👍 1

anonfunc commented

2021-11-14 21:32:37 +01:00

Owner

Could this also be done automatically by comparing whether the package contents are the same as in upstream package?

If I remember correctly the reproducible builds check does something similar (although with a different goal). Seeing how that is done could be a possible first step to automate this. Will have a look at that tool later.

> Could this also be done automatically by comparing whether the package contents are the same as in upstream package? If I remember correctly the reproducible builds check does something similar (although with a different goal). Seeing how that is done could be a possible first step to automate this. Will have a look at that tool later.

anonfunc referenced this issue

2022-05-29 23:07:30 +02:00

[Suggestion] Blacklist Nvidia drivers #126

anonfunc referenced this issue

2023-12-27 22:34:41 +01:00

vivaldi in its current form does not make sense to be in the ALHP repo #226