(create page) |
(→Scope) |
||
| Line 68: | Line 68: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: | * Other developers: fix any identified issues <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 74: | Line 74: | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
* Policies and guidelines: N/A | * Policies and guidelines: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
Revision as of 14:40, 7 July 2017
Drop 256term.sh
Summary
Do not install /etc/profile.d/256term.sh and /etc/profile.d/256term.csh.
Owner
- Name: Zbigniew Jędrzejewski-Szmek
- Email: zbyszek at in.waw.pl
- Release notes owner:
Current status
- Targeted release: Fedora 27
- Last updated: 2017-07-07
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Currently Fedora installs some scripts to be executed every time a shell is started which perform some heuristics to set $TERM based on the terminal emulator being used. This is a work-around and it's better to for the terminal emulator to set $TERM properly on its own. Various terminal emulators have been updated to do that. /etc/profile.d/256term.sh and /etc/profile.d/256term.csh will not be installed anymore and the $TERM variable set by the terminal emulator will be used.
[The change is trivial in and of itself. I'm making this a system wide change, and a change at all, only because those scripts take part in every shell startup, so it's possible they will have some unforeseen impact or require adjustments in other components. If FeSCO or Wrangler think this does need a change page, I'm ready to drop it.]
Benefit to Fedora
The environment is initialized in a simpler, more predictable way. A step is made towards removing initscripts package. The common path in shell startup is slightly optimized. Less used shells and terminal emulators work out-of-the-box the same as the popular ones.
Scope
- Proposal owners: do the change in initscripts package, work with other developers to fix any identified issues.
- Other developers: fix any identified issues
- Release engineering: [1]
- List of deliverables: N/A
- Policies and guidelines: N/A
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
The change will take effect on old and new systems in the same way when the updated initscripts package is installed.
How To Test
Make sure that $TERM is set properly in various circumstances (a shell open in a terminal emulator, a ssh connection from a Fedora machine to a different machine, a shell connection from a different machine to Fedora, screen session, tmux session, etc.) and that stuff is displayed properly.
User Experience
Should not be noticeable.
Dependencies
None.
Contingency Plan
Restore those two scripts.
- Contingency deadline: beta freeze
- Blocks release? No
- Blocks product? No
Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=1165439
Release Notes
None needed.