Arch Linux User Repository

@Eli

Your argument is absolutely justified. I adopted this package about five years ago when it already skipped the checksum and simply downloaded the pre-compiled josm-latest.jar. I maintain this primarily for legacy reasons and because it is rather convenient to use this in a pre-compiled form:

• Download might be quicker (unless you keep the svn directory)
• Official build (non-reproducible because of private build script; but you don't know what you get)
• Compilation requires additional dependencies and takes a long time (about one minute on my machine, but that is expected from source packages)

All in all there are no clear pros and cons (except for the crude implementation at the moment). I'll provide an SVN version shortly (when it is tested), but keep this package for a while with a legacy warning so that users have time to change to the new version.

Umm...

Why don't you just create an svn package which clones the svn sources, then runs "ant dist" to create the latest version?

I'm entirely unsure why you're doing such elaborate magic instead, especially considering "latest" is an inaccurate name.

This also avoids the issue where you've disabled checksums because you want to use nightly binaries but cannot be bothered to do any checking whatsoever, so even if the download is truncated you'll happily consider the package a success. There's a reason why checksums exist...

It happened! Automatic updates are now live. If you notice any strange behavior or if you think that this is a really bad idea, please leave a comment (and ideally a suggestion for a better method).

Just a quick heads-up: I prepared an automatic update script of this package. I will monitor it for a few days and enable it at the weekend.

What will it do?

It checks for a new version of JOSM every hour and updates the package in the AUR if necessary.

Why will it do this?

Because I get a lot of out-of-date flags for this package just because people do not understand how it is designed.

Why is/was it designed this way?

This package builds from the nightly build of JOSM (called "josm-latest"). This means it will change probably more than once a day. Thus the checksums are skipped and pkgver() will set the correct version. It downloads a binary, so I cannot use VCS magic.

The downside is that you won't get an update notification and if you cache the downloaded files, makepkg will not re-download them. This is a problem and I assume that some people were affected by this.

The new version will not contain checksums as well because I want the package to be built in every situation. This might result in an outdated version code, but this would last for less than a day anyway. I might improve it in the future if I get an Idea how to do it.

Sorry, my bad... I did read the pinned, but thought something was still wrong. I'm working on an AUR wrapper script. "Pacman -Sl aur" showed "aur josm-latest 13473-1" in my AUR repo. I manually built your package to double check with results below. Definitely newer than off. repo version. Now to figure out my script issues. Thanks quick reply!

==> Finished making: josm-latest 13548-1 (Mon Mar 19 15:36:19 PDT 2018)

@Cody_Learner Because this is the nightly version which is much newer than the stable version from the official repo. Please read the comments, especially the pinned one.

A newer version of this package is available in the official repos. Why is this still here?

$ pacman -Ss josm community/josm 13500-1 [installed]

Doesn't work anymore. Instead of "logo.png" there are now seven logo images in different sizes and colour depths in the image folder. You may change "images/logo.png" to e.g. "images/logo_48x48x32.png" in the PKGBUILD.

Your package josm-latest has been flagged out-of-date by strebski mayby better option is to remove this package from AUR repository?

Why do you think that this package should be removed? It is up-to-date and I use it almost daily. Please read the comments.