Bug 429239 - diveintopython-txt is (almost) empty
Summary: diveintopython-txt is (almost) empty
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: diveintopython
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Marc Wiriadisastra
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-18 05:01 UTC by Mohd Izhar Firdaus Ismail
Modified: 2008-01-19 01:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-19 01:05:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mohd Izhar Firdaus Ismail 2008-01-18 05:01:18 UTC
Description of problem:
diveintopython-txt only contains 
/usr/share/applications/fedora-diveintopython-txt.desktop
/usr/share/diveintopython-txt/

Version-Release number of selected component (if applicable):
diveintopython-txt-5.4-6.fc9

How reproducible:
Always

Steps to Reproduce:
1. yum install diveintopython-txt
2. rpm -ql diveintopython-txt
  
Actual results:
diveintopython-txt should provide or pull dependency for
/usr/share/diveintopython-txt/diveintopython.txt as the desktop file tries to
xdg-open /usr/share/diveintopython-txt/diveintopython.txt

Expected results:
clicking the desktop file should open the document

Additional info:
imo, diveintopython doesnt need to provide .desktop file, especially for the
-txt and -html where it will possibly start up gedit/firefox which might not be
desirable. Plus the other diveintopython-* provides .desktop files with the same
Name tag, and it can confuses users. Furthermore, iirc, .desktop files are meant
for launching applications, not documents.

Comment 1 Marc Wiriadisastra 2008-01-19 01:05:31 UTC
It uses xdg-open so that shouldn't be an issue it will default to whatever is
the preference on the desktop you are using.

When I went through the review process I was allowed the desktop files so I have
left them in there. I personally don't see a reason to remove them.

The issues are fixed in the next version btw.


Note You need to log in before you can comment on or make changes to this bug.