Hello,
not so long time ago, the new version of Fish got released which contains some number of backward-incompatible changes, though most of them are done towards making fish behave same as other shells.
I didn't see anything broken on my system due to that with default installation or with oh-my-fish.
Search for Notable non-backward compatible changes on https://github.com/fish-shell/fish-shell/releases/tag/3.0.0.
Notable non-backward compatible changes
I would like to ask FESCo for exception to make this update in F29 since it brings quite some number of useful features (e.g. adding &&, ||).
&&
||
i'm of the opinion that we should not make backwards incompatible changes for the sake of features. Fedora 30 will be available soon enough.
Also, this can be provided trough a Copr repo or a module or whatnot in case people actually ask for it.
I'll vote +1. I know that we have a general rule to avoid backwards incompatible changes, but in this particular program, looking at the linked list, it's mostly very special corner cases. E.g. I hope that nobody relies on {,,,,} expanding to , and ,. Also, fish is mostly used for interactive work, where this kind of small changes are not a big concern, but new features and improved compatibility with other shells is. I think we should allow this: cautious updates of packages directly visible to end users.
{,,,,}
,
Adding to the meeting agenda since it has -1 votes.
Metadata Update from @sgallagh: - Issue tagged with: meeting
I've created modular updates for F28 and F29.
Also proposed to change defaults: https://pagure.io/releng/fedora-module-defaults/pull-request/46
This was discussed in FESCo meeting 2019-01-14: AGREED: FESCo does not grant an exception to the stable updates policy for 'fish' and recommends the use of a module stream or COPR repository instead. (+6, 0, -0) (sgallagh, 16:43:02)
@ignatenkobrain thank you for creating the modular updates.
Metadata Update from @zbyszek: - Issue close_status updated to: Rejected - Issue status updated to: Closed (was: Open)
Metadata Update from @churchyard: - Issue untagged with: meeting
Login to comment on this ticket.