Newbie here:
Simple and short: what is it and how does it work?
When I click on “1-click install” I get a webpage with a script which does nothing. Do I need to do something else than just clicking? If so, why is it called 1-click install?
Please help. Thank you.
Where? Can you please give at least one example to enable others to recreate what you did?
I looked at a thread about creating a Mcc like interface: https://forums.opensuse.org/showthread.php/513426-Mac-achtige-taakbalk-in-Leap
Knurpht wrote this web address: https://software.opensuse.org/package/cairo-dock
When I open the page and click on the line which says Leap 42.1 I see: 1-click install.
Clicking it gives me the webpage with the script.
Which web browser do you use? When I click on such a link, my Firefox (btw, I am on 13.1, but that happened also in earlier versions, thus why not in 42.1?) shows me a pop-up that offers me two options (I have it in Dutch, but this is what I think it says):
cairo-dock.ymp
this is: YaST Meta Pckage
from: https://software.opensuse.org
What shoudl Firefox do with this file?
That’s it Henk, I use Chrome and I see only this:
<metapackage xmlns:os="http://opensuse.org/Standards/One_Click_Install" xmlns="http://opensuse.org/Standards/One_Click_Install"> <group>
<repositories>
<repository recommended="true">
<name>home:yield65</name>
<summary>yield65's Home Project</summary>
<description>Please add a suitable description and don't forget to add some repositories you want to build your packages against (just click on 'Repositories' above). Have fun!</description>
<url>http://download.opensuse.org/repositories/home:/yield65/openSUSE_Leap_42.1/</url>
</repository>
<repository recommended="false">
<name>openSUSE:Leap:42.1</name>
<summary>openSUSE Leap 42.1</summary>
<description></description>
<url>http://download.opensuse.org/distribution/leap/42.1/repo/oss/</url>
</repository>
</repositories>
<software>
<item>
<name>cairo-dock</name>
<summary>A small simple but effective doclet like Mac</summary>
<description>Cairo-dock was in the beginning a small simple but effective dock.
On 4th July 2007, Fabounet proposes to us a version improved,
with a very ergonomic configuration, on the ubuntu-fr.org forum.
Since, new versions are followed at an intensive pace and with
their new functionalities like the sub-docks, the effects on
the launchers ... Many people are grafted with the project,
each one bringing its competences, of graphics, to the applet
or plugins and development.</description>
</item>
</software>
</group> </metapackage>
Opening the page in Firefox gives me the pop up to install the software. Still wonder why it is called 1-click software because I needed to click many times before the install started.
So, it is a difference between Chrome and Firefox.
Thanks for your help.
You are welcome. I guess the Firefox (being adapted for the openSUSE distribution) acts on the suffix .ymp, which is a rather special one.
I assume it is called “1-click” because before it was “invented” you had to do several things (starting YaST to add a repo, starting YaST to install the package, etc.) while this one click starts a single sequence where you can not easily forget things.
Nevertheless, it is always wise to contemplate about the question if you want to keep the repo registered or not. I mostly go to YaST and disable a repo that is only used for a single (or very few) package(s), to avoid later clashes.
This might be worth requesting someone to create a package to provide this functionality in Chrome (and other browsers that aren’t installed from the OSS repo).
This functionality you’re looking at is called a “MIME Type.”
All browsers contain a file that maps file extensions to some application, plugin, or part of the browser that knows how to handle that type of file.
It’s a fairly standard entry, my guess is that it might be completely portable between browsers so the Firefox code might work in Chrome with hardly any modification. Who knows, maybe someone can get the code accepted upstream in Chromium (which might then eventually make it into Chrome).
So, it’s worth submitting a feature request to
https://bugzilla.opensuse.org
It’s the kind of thing that might take very little time for someone to create which affects many people.
TSU
That is not quite true. The HTTP cllient (browser) does not recognise Windows filename extensions, nor does it recognise suffixes on filenames (which look very much the same).
HTTP clients however detect the MIME type of a file send by the HTTP server by interpreting the HTTP header field Content-Type. Example:
Content-Type: text/html
It is the HTTP server that creates this HTTP header field. It depends on the HTTP server, but Apache does so (indeed) by, looking at the suffix of the file name it is going to send (this is a simplification, like in many cases Apache can do more complicated things to decide which MIME type to send).
I am running Apache and I find in it’s default configuration file /etc/apache2/mime.types:
text/x-suse-ymp ymp
.
Thus when it is asked to send a file where the name has the suffix (or on a Microsoft system the extension) .ymp, it will send within the HTTP header
Content-Type: text/x-suse-ymp
As the subtype x-suse-ymp starts with x-, it belongs to the Unregistered x. tree, of which Wikipedia states:
The “x.” tree may be used for media types intended exclusively for use in private, local environments and only with the active agreement of the parties exchanging them. Types in this tree cannot be registered.
Thus there can not be any obligation for Chrome to implement this.
So this is the MIME type the browser must be able to handle. And when asking for Chrome to do that, the request must be for implementing the MIME type x-suse-ymp and NOT for implementing based on the .ymp suffix.
FWIW, the discussion in this bug report may be of interest to the OP:
That’s a really good bug discussion, the last post includes a link to an openSUSE package which should fix Chrome.
TSU