Pacup and connecting your pacscript with repology. #845
Replies: 6 comments 5 replies
-
It would be nice to know what pacup actually updates by itself in the pacscripts instead of just saying "semi-automate" |
Beta Was this translation helpful? Give feedback.
-
Everyone disregard git packages. |
Beta Was this translation helpful? Give feedback.
-
microsoft-prod-repo-deb and kxstudio-repos-deb doesn't have a repology page |
Beta Was this translation helpful? Give feedback.
-
What should I do for unique packages like aomp. Because Pacup may downgrade it! |
Beta Was this translation helpful? Give feedback.
-
There has been a change in how pacup's repology parser works (to allow for packages like Sorry for the inconvenience, I'll update the wiki soon, and refactor your PRs regarding repology integration myself. |
Beta Was this translation helpful? Give feedback.
-
Here is the update for the packages I maintain Merge requested: Will never receive updates: Depend on an issue (pacstall/pacup#32): Don’t have repology project (or only pacstall): |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey maintainers, we're making a new automated tool which will help you update your pacscripts with ease. It's called Pacup (not released yet).
For Pacup to work you need to add a
repology
variable to your pacscripts. Pacup will use this variable to track the pacscript's packages latest version, and semi-automate the pacscript updating process for you.Here's a list keeping track of the which pacscripts have been updated with the
repology
variable:brave-keyring-deb by @Zahrunferdi-deb by @Zahrunkxstudio-repos-deb by @echometerainmicrosoft-prod-repo by @echometerainwazzapp-deb by @Zahrunaomp-deb by @cat-master21Beta Was this translation helpful? Give feedback.
All reactions