AUR (en) - jrosetta

Search Criteria

Package Details: jrosetta 1.0.4-5

Git Clone URL:	https://aur.archlinux.org/jrosetta.git (read-only, click to copy)
Package Base:	jrosetta
Description:	Graphical console engine for Swing
Upstream URL:	http://dev.artenum.com/projects/JRosetta/
Licenses:	GPL2
Submitter:	td123
Maintainer:	MRWITEK
Last Packager:	MRWITEK
Votes:	28
Popularity:	0.000000
First Submitted:	2011-12-07 20:36 (UTC)
Last Updated:	2020-12-12 15:50 (UTC)

Git Clone URL:

https://aur.archlinux.org/jrosetta.git (read-only, click to copy)

Package Base:

jrosetta

Description:

Graphical console engine for Swing

Upstream URL:

http://dev.artenum.com/projects/JRosetta/

Licenses:

GPL2

Submitter:

td123

Maintainer:

MRWITEK

Last Packager:

MRWITEK

Votes:

Popularity:

0.000000

First Submitted:

2011-12-07 20:36 (UTC)

Last Updated:

2020-12-12 15:50 (UTC)

Latest Comments

1 2 Next › Last »

MRWITEK commented on 2015-05-12 17:21 (UTC)

Upstream is currently dead.

MRWITEK commented on 2015-04-24 20:47 (UTC)

Reported upstream. Meanwhile, you can use this: https://www.dropbox.com/s/f35kiamng3nj18q/jrosetta-api-1.0.4.jar?dl=1 https://www.dropbox.com/s/tfx4m3u4fcxoj8l/jrosetta-engine-1.0.4.jar?dl=1

plasmapotato commented on 2015-04-24 19:42 (UTC)

404 not found Source urls aren't working

alucryd commented on 2012-02-15 09:28 (UTC)

Alright, package updated.

alucryd commented on 2012-02-14 14:20 (UTC)

Yep I know (though it shouldn't be needed), but my arch box is dead right now, I'll update the pkgbuild as soon as I have it restored^^

<deleted-account> commented on 2012-02-14 11:19 (UTC)

this one worked to me, just add this line to the PKGBUILD noextract=("jrosetta-engine-$pkgver.jar" "jrosetta-api-$pkgver.jar")

alucryd commented on 2012-02-12 22:01 (UTC)

Oh I took a day to try and build scilab not long ago, that's why I have all those packages around. But I didn't succeed, some package from the official repo isn't recognized by configure (forgot which one), another from aur wasn't either. Only solution is to build their prerequisites tarball, and I don't like that. In the end I just gave up. Good luck to you.

<deleted-account> commented on 2012-02-12 21:57 (UTC)

Yes, bdstar (on behalf of yaourt) really did try to extract them, as seen in the output below. I don't understand what this page (http://code.google.com/p/libarchive/issues/detail?id=225) says but I think it's relevant and the extraction attempt is a bug. It never ocurred to me to try installing with noextract AND not extracting them manually so that may well work and it's actually not necessary to manually extract. Sadly I'm in the middle of building Scilab so I can't test that right now.

alucryd commented on 2012-02-12 21:41 (UTC)

Well the JARs are not meant to be extracted, rather they are copied as is in /usr/share/java. Did bdstar really try to extract them? I wasn't aware of that, and if that's the case, noextract is the right way to prevent it and it should be added to the pkgbuild. However I don't understand why you had to manually extract the JARs.

<deleted-account> commented on 2012-02-12 21:25 (UTC)

OK I solved that problem by adding this line after the sources=("... line: noextract=("$pkgname-api-$pkgver.jar" "$pkgname-engine-$pkgver.jar") I then manually extracted the archives and it has installed