We all know that portage has many a ebuild that aren't being version bumped for a long time, and when they're finally bumped it amounts to a simple version number change. For example, app-misc/worker(which is near and dear to my heart) is at 3.8.3, a 5 YEAR OLD release, even though nothing in its build process have changed, and you can use the same precise ebuild with a 2 week old version. So, why should a person maintain something that works - go to a website, look up version change, bump it manually? Github in particular will redirect you from release/latest to the actual latest release. Many a software are either hosted on github or have latest release page. Why not just periodically grep out the latest version from that page, bump the ebuild, and(if it's compiling without errors) bump it? I bet this could simplify maintenance and bring us closer to the bleeding edge. An example script doing just that is in the url field. And why should this be a script? I'm throwing this idea out to you fine gentoomen, who actually write portage. This could be a feature for the maintainers, or just the feature within portage itself, wherein you could autobump your packages that have ``latest" url with a command. Reproducible: Always Steps to Reproduce: 1. Look at the script 2. Consider the possibilities Actual Results: mind==blown
Not a bug and bugzilla is not a discussion forum. There are many reasons why this won't work either. Builds are not universal even between versions of the same package. For more discussion, this is best for the gentoo-dev mailing list.
