caldurza / autokey

Automatically exported from code.google.com/p/autokey
GNU General Public License v3.0
0 stars 0 forks source link

two problems with the desktop file #88

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by wobbe...@gmail.com on 6 Oct 2010 at 11:36

GoogleCodeExporter commented 8 years ago
Sorry, 

When I want to install autokey-gtk-0,71.0 on OpenSUSE I get two remarks about 
the desktop file.

One is that the Category is not right. I must be like this Categories=GTK;GNOME;

Second is that the Icon has a fixed url. 

Regards,

Roelof Wobben

Original comment by wobbe...@gmail.com on 6 Oct 2010 at 11:38

GoogleCodeExporter commented 8 years ago
I believe the categories are correct by Debian standards, as Luke brought that 
file up to code a while back. I don't know much about the icon path issue, Luke 
would you care to comment?

Original comment by cdekter on 6 Oct 2010 at 12:15

GoogleCodeExporter commented 8 years ago
I've corrected the Categories in r300, and the absolute pathnames in r301. 
Please let me know if the contents of trunk are okay for your purposes. 

Original comment by Luke.Faraone on 6 Oct 2010 at 2:41

GoogleCodeExporter commented 8 years ago
Hello Luke, 

I downloaded the tar.gz file from the downloads section.
But i can't find which r that is.

Does a new .tar.gz come out that contains r300 en r301

Roelof

Original comment by wobbe...@gmail.com on 6 Oct 2010 at 3:47

GoogleCodeExporter commented 8 years ago
It will be in the next release. "r300" refers to a revision number in SVN.  You 
can access the svn trunk at http://code.google.com/p/autokey/source/checkout

Original comment by Luke.Faraone on 6 Oct 2010 at 4:30

GoogleCodeExporter commented 8 years ago
oke, 

I will wait till the next release and try to solve this problem temporarly with 
some  sed commands.

Thanks  for the help,

Roelof

Original comment by wobbe...@gmail.com on 6 Oct 2010 at 6:05