[aur-general] Eclipse plugin packaging standardization proposal

[bardo]

First of all, nobody really wrote /against/ this proposal and nobody
said there's no need for a standard, so I suppose everyone's ok with
it. If this is not the case, just speak up, otherwise I'll wait for a
week from the last comment and then proceed to wikify it.

On Thu, Nov 20, 2008 at 5:37 PM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> / syntax is actually for replacement. The syntax above says "replace
> with nothing". The # and % syntax is for deletion (matching from the
> front or back of the word, respectively). I doubt there's any real
> difference as far as performance goes.

I'll keep the slash syntax, then, it's also simpler to customize.
Thanks fo the great explanation :)

>> (2) you could use the jar command to extract a jar file instead of
>> unzip. that's what it's made for. it's in the jdk which is a dependancy
>> of eclipse. so you can expect user to have jar command and jdk package
>> (jar is also in java-gcj-compat)

I modified the PKGBUILD to use jar instead of unzip, thanks. However I
had to do some other changes. As I pointed out in the post:
«I was noticed that I can directly use jar, which the user already has
since it's part of the JRE. This is great, since it spares a
makedepend! However, jar can't extract to directories other than the
current one: this means that, after the directory creation, it's
necessary to cd before extracting. Since there were many occurrences
of the destination path I decided to use a custom variable even though
somebody might not like it, because there's a great improvement in
readability.»

Quick link reference:
http://blog.bardland.org/2008/11/20/arch-linux-eclipse-plug-in-packaging-a-proposal/


Corrado