Bug 1395661 - Package resize(1) somewhere else
Summary: Package resize(1) somewhere else
Keywords:
Status: CLOSED DUPLICATE of bug 1349582
Alias: None
Product: Fedora
Classification: Fedora
Component: xterm
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 11:30 UTC by Dr. David Alan Gilbert
Modified: 2016-11-16 12:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-16 12:47:21 UTC
Type: Bug


Attachments (Terms of Use)

Description Dr. David Alan Gilbert 2016-11-16 11:30:02 UTC
Description of problem:
The 'resize' command is packaged as part of xterm, however based on the usage of resize it should be packaged somewhere which doesn't have the dependencies on X; however, I'm not sure the best place for it to live.

resize(1) finds the size of the current terminal by the use of ANSI escape codes; it's use is pretty obscure these days, but it's main use is where you're logged in via a remote serial console (e.g. via a console server, ipmi or these days more likely via a VM serial console).

resize(1) gets run on the remote device - i.e. the device you're talking to over serial; and so there's no need for that machine to be running X and hence installing xterm on that host (with all it's dependencies) makes no sense.

Similarly if I'm using any terminal other than xterm I'd still want to use resize.

It's only dependency is libtinfo (ncurses-libs).

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dr. David Alan Gilbert 2016-11-16 11:31:04 UTC
forgot to mention; this came about from a discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1149651

Comment 2 Miroslav Lichvar 2016-11-16 12:47:21 UTC
There is a similar request in bug #1349582.

*** This bug has been marked as a duplicate of bug 1349582 ***


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