3 ms·
Running 3rd party packaging repos does work, and we do it at Keybase, but it's surprisingly annoying. Distro upgrades disable your repo by default, and your pac
by oconnor663 10y ago
Running 3rd party packaging repos does work, and we do it at Keybase, but it's surprisingly annoying. Distro upgrades disable your repo by default, and your packages need to install a cronjob to detect when it happens and fix it. And because that scenario is difficult to test, you inevitably get bugs like this one: https://bugs.chromium.org/p/chromium/issues/detail?id=660145 https://bugs.chromium.org/p/chromium/issues/detail?id=660145
So it works, but I really wish we didn't have to maintain it.
- majewsky 10y ago> Distro upgrades disable your repo by default Have you considered filing a feature request with the distributions about this? I can see why they do it this way, but there are certainly ways around this problem. (For example, a repo's metadata could include references to the identical repo for other OS versions, so that an upgrade can automatically switch to the appropriate repo.)
- Arizhel 10y agoThis definitely sounds like a bug to me. Assuming your company is maintaining 3rd-party repos for both the older and newer versions of the distro, doing a distro upgrade should, logically, switch to your repo for the newer OS version automatically, so it's completely seamless to the user. If the distro isn't doing that, that seems like an oversight.