Bug 155993 - 'gv' gone from the search path breaks existing scripts and expectations
'gv' gone from the search path breaks existing scripts and expectations
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: gsview (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Rex Dieter
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-26 10:49 EDT by R P Herrold
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-26 11:06:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description R P Herrold 2005-04-26 10:49:05 EDT
The elimination of 'gv' from the search path breaks prior expectation.  This
patch adds the needed courtesy link to avoid breaking expectation and the
principle of 'least surprise'.

Dunno if thre is a 'new and improved 'gv' on the horizon, but ggv is clearly not
is, from a performance and feature standpoint.  If this is the plan, gsview and
ggv integration with 'alternatives' is needed. 

[herrold@centos-4 SPECS]$ diff gsview-old.spec gsview.spec
6c6
< Release: 10
---
> Release: 11orc
66a67
> ln -s %{_bindir}/gsview $RPM_BUILD_ROOT%{_bindir}/gv
96a98,101
> * Tue Apr 26 2005 R P Herrold <info#owlriver.com>  4.6-11orc
> - remove silent Epoch in changelog versioning,
>   add 'conform to expectation' gv link
>
[herrold@centos-4 SPECS]$     



Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Rex Dieter 2005-04-26 11:06:18 EDT
I seriously doubt this patch would ever be accepted (and I have personal
reservations about gsview falsely masquerading as gv).

It would be more appropriate to raised the issue on the fedora-devel mailing list.

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