Bug 91223

Summary:	Package Gnus separately
Product:	[Retired] Red Hat Linux	Reporter:	Tim Landscheidt <tim>
Component:	emacs	Assignee:	Jens Petersen <petersen>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	low
Version:	9	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-01-15 01:35:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Landscheidt 2003-05-20 04:09:05 UTC

ATM, Gnus is packaged as a part of Emacs. As Gnus' development cycle is not so closely 
connected to Emacs', updates of Gnus - whether keeping up with the Oort betas in the past or 
installing the current release 5.10 - are pretty complicated. 
 
It would be nice if Gnus was delivered as a separate package that can be updated separately 
as well. This amounts to just a little tweaking of emacs.spec.

Comment 1 Jens Petersen 2003-05-20 07:37:52 UTC

I sympathize with your suggestion.  It looks like gnus will finally
get updated in xemacs-sumo in the next release for example....

On the other hand I'm not keen on ripping stuff out of emacs, since
gnus is to some extent integrated into Emacs.

It is not that hard to install gnus in an elisp directory of one's own
or a system-wide site-lisp directory though...

Comment 2 Tim Landscheidt 2003-05-31 20:23:01 UTC

Your argument is coherent - so I adjust my plea: Provide separate packages for 
Gnus releases that are not shipped with the current Emacs :-).

Comment 3 Jens Petersen 2004-01-15 01:35:19 UTC

I suggest this is something for Fedora Extras (ie fedora.us).
If you or someone submits a gnus package there, that passes
qa, I think it will be accepted.