Re: Fedora 34 Change: Deprecate xemacs, xemacs-packages-base, xemacs-packages-extra, and neXtaw (Self-Contained Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2020-12-30 at 14:53 -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Deprecate_xemacs
> 
> 
> == Summary ==
> Deprecate the xemacs, xemacs-packages-base, xemacs-packages-extra,
> and
> neXtaw packages, all of which have dead upstreams.
> 
> == Owner ==
> * Name: [[User:jjames|Jerry James]]
> * Email: loganjerry@xxxxxxxxx
> 
> 
> == Detailed Description ==
> 
> I have been part of XEmacs upstream for over 20 years, and have
> maintained the Fedora package for over 11 years.  Upstream
> development
> had already slowed significantly when I became Fedora maintainer. 
> The
> last release was over 7 years ago.  Since that time, development has
> essentially come to a halt.  Somebody will push a commit every now
> and
> then, but significant bugs are not being fixed.  I see no future for
> the project.  We should start moving towards dropping it from the
> distribution.  The upstream sources have been spread across 3
> packages
> in Fedora: xemacs, xemacs-packages-base, and xemacs-packages-extra.
> In addition, the xemacs package uses an ancient, unmaintained 3D X
> library: neXtaw.  It's last release was in 2003.  Since xemacs is the
> only package in Fedora that uses neXtaw, I propose that it also be
> deprecated so we can eventually drop it.
> 
> Deprecation is warranted because there are about a dozen XEmacs add-
> on
> packages in Fedora.  This will prevent us from adding any more as we
> work to retire the existing add-ons.
> 
> == Feedback ==
> 
> On December 7, 2020, I
> [
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/VDETPULZDBMXBXJKEFZX7DQ5R6W6FBXT/
> communicated my intent to file this Change] on fedora-devel-list.
> There has been no community feedback.
> 
> == Benefit to Fedora ==
> 
> This Change will open a path for us to eventually remove unmaintained
> software from the distribution.
> 
> == Scope ==
> * Proposal owners:
> The only required work is the addition of `Provides: deprecated()` to
> the 4 affected packages.
> 
[snip]

I see this documented here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packages/#_consequences_of_a_package_being_deprecated

but not in the packaging guideline:
https://docs.fedoraproject.org/en-US/packaging-guidelines/

and IIRC fedora-review does not require this check either. I think it's
probably quite safe to assume the risk of someone creating a new
package that depends on xemacs or neXtaw to be quite low, but should
the main guidelines and fedora-review be updated too? (separately from
this Change, that is).

I must admit this is the first time I noticed `Provides: deprecated()`

Best regards,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/michel@xxxxxxxxxxxxxxx
chat via email: https://delta.chat/
GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux