Chromium-browser-bin uses continuous builds of Chromium - the same way firefox-nightly uses continuous nightlies of Firefox. The only difference being that Google names the builds according to the build version - Firefox according to the actual version number. Thus, if one is to create a decent package for the continuous chromium builds, he or she should have a package looking for the latest build number - whether or not the pkgver shown in AUR is the actual latest build number or, as in this case, something like "LATEST" is irrelevant. It's the maintainer's call and the current implementation is simpler. It's NOT the case here.
So no, "7.latest" would not make me happy. JRE is not a continuous build project. It's a project with clear different releases. First there was "7", now there was "7u1". The next one is going to be... that's right, "7u2".
Maybe you should just give this package up. You still haven't "pulled" the changes I suggested 2 days ago anyway.
Search Criteria
Package Base Details: jdk
Package Actions
| Git Clone URL: | https://aur.archlinux.org/jdk.git (read-only, click to copy) |
|---|---|
| Submitter: | td123 |
| Maintainer: | dbermond |
| Last Packager: | dbermond |
| Votes: | 1087 |
| Popularity: | 0.22 |
| First Submitted: | 2011-08-27 17:56 (UTC) |
| Last Updated: | 2024-04-26 00:51 (UTC) |
Det commented on 2011-11-27 19:04 (UTC)
Det commented on 2011-11-27 18:45 (UTC)
Ehm... and you can't just check the upstream's home page for the latest version of JDK?
Have a look: http://www.oracle.com/technetwork/java/javase/downloads/index.html. What does it say?:
"Java SE 7u1
This release includes many security fixes.
Learn more"
Oh my gosh! I was wrong after all!
Det commented on 2011-11-27 18:43 (UTC)
Well, the thing is that I don't have to ask. Using dserban's logic google-chrome* packages wouldn't need to be updated either - but they are. Because it's _right_.
Babets commented on 2011-11-27 18:31 (UTC)
Det you are right, you can ask to some trusted user in aur-general mailing list for opinions and if they say you are right you can ask for orphaning this package.
Det commented on 2011-11-27 18:28 (UTC)
Right...
1) I have only flagged this package once, jre twice.
2) What the _hell_ do you mean with a "build log". JDK "7u1" has been released over a month ago - this one says it's "7", Q.E.D.: it's out-of-date.
Why is it so hard to understand?
Det commented on 2011-11-27 14:19 (UTC)
Nope, it doesn't.
Det commented on 2011-11-27 14:16 (UTC)
That's not the point here.. the package downloads whatever is the latest version in the Oracle servers (effectively skipping the md5sums too). The problem is that this is not a git package - if you don't touch the pkgver people don't know when a new one has come up.
If you can't or won't understand that you have chosen the wrong package to maintain to begin with.
Pinned Comments
dbermond commented on 2024-03-19 19:54 (UTC)
As was made with the java packages in the official repositories, jdk now provides the jre alongside it, and both packages conflict with each other. During the package upgrade to version 22, act accordingly to your needs. For example, if you have both jdk and jre installed, only jdk will be sufficient, as it now also contains the runtime environment, and jre can be uninstalled. If you have only jre installed, no action is required.