Arch Linux

hmm

sed -e '/application\/x-java-jnlp-file/d' -i /etc/mailcap

would be better than this grep action. Other option is using a tempfile which is created by piping through grep -v, I would prefer the sed method, as it's cleaner.

Probably the reason for using grep is the fact that it is more common than sed. However grep should be added to jre's dependency list too.

grep and sed are both base packages, so there's no about "what's more common" ;)

I have this problem too. May be it should be marked something more than LOW since having a broken /etc/mime.types can have relevant consequences in certain environments: I have sent several unreadable mail attachments with mutt, since the attachment was encoded in the wrong way.

I have this problem too. I only noticed it because Firefox can't offer me a default app to open files so I need browse to the executable myself every time.

I had this problem too. Fixed it by deleting /etc/mime.types are reinstalling the package, but this is really annoying!

Is this fixed yet? We shouldn't even be touching mime.types in the jre and other install files as this type is already there to begin with if you install the mime-types package.

Shouldn't this be assigned to Jason, as maintainer of this package?

But more productively, Dan can we really just get rid of the touching of mime.types entirely, or are we going to need to find a safer way to do this?

Jason, do you want me to take a crack at this?

If so, let me know and I will.

If the mime.types line is in there, great, but how will we automatically add the web start line to mailcap? That's the whole reason these scripts are run in the first place.

Feel free to try Paul.

Paul- I have an updated mime-types PKGBUILD sitting around that I've never pushed, but I don't think that is the holdup here. We shouldn't have to touch mime.types, so we should focus on the mailcap issue.

So as I understand this:

1) We can just never touch mime-types.

2) Jan's solution above seems safe for mailcap and addresses the \n issues.

So does this attached jre.install seem to everyone like it would solve the problems? If so, I'll go ahead and test/deploy it. But I didn't want to go any further without being sure I understood the issues-- this seems a little too simple to me to be the answer.

I have tested the new jre.install in all the four scenarios I imagined:
1) first installation of jre and no /etc/mailcap in the system;
2) upgrade of jre and no /etc/mailcap;
3) first installation and existing /etc/mailcap;
4) upgrade and existing /etc/mailcap.
In all the four scenarios, it seems to do the right thing. So, when there is no /etc/mailcap, a single line /etc/mailcap is created with:

application/x-java-jnlp-file;/opt/java/jre/bin/javaws %s

When /etc/mailcap exists, this line is added at the end of the file, without damaging the rest of the file; also the \n are untouched.

Obviously also /etc/mime.types is now not damaged.

It seems to me that this simple solution works fine.

Oh, and finally I tested also the remove scenarios: if I remove jre when that file includes only that line, then the file is removed. If it includes also other things, then only that line is deleted and the file is not damaged.