7:25 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
texinfo-1.29-pkg.tar.gz upstream version: none
text-modes-1.85-pkg.tar.gz upstream version: none
Previously Announced Packages Still in Pre-Release:
==================================================
gnus-1.84-pkg.tar.gz upstream version: 5.10.7
mail-lib-1.72-pkg.tar.gz upstream version: none
mh-e-1.29-pkg.tar.gz upstream version: 7.4.2
net-utils-1.45-pkg.tar.gz upstream version: N/A
re-builder-1.02-pkg.tar.gz upstream version: 1.20
riece-1.19-pkg.tar.gz upstream version: 1.0.8
tramp-1.23-pkg.tar.gz upstream version: 2.0.48
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/texinfo/ChangeLog -------
2005-03-26 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.29 released.
2005-02-23 Katsumi Yamaoka <yamaoka(a)jpl.org>
* texinfmt.el (texinfo-format-scan): Silence whitespace-cleanup.
* texnfo-upd.el (texinfo-copy-node-name): Use point-at-eol instead
of line-end-position.
- ------- ChangeLog Entries from xemacs-packages/text-modes/ChangeLog -------
2005-03-26 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.85 released.
2005-03-25 Aidan Kehoe <kehoea(a)parhasard.net>
* whitespace.el (whitespace-cleanup): Integrate this change from
the FSF:
2003-06-10 Rajesh Vaidheeswarran <rv(a)gnu.org>
* whitespace.el (whitespace-cleanup): Respect user
preference for silence.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
norbert - XEmacs Package Release Manager.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCRbcjgu3ywdHdhM0RArIBAKCTVUR1VpOsJ/vQaiJ+apcSizeQQACdHVYF
pcd4KMADQt1rzfwporn88Nk=
=BieO
-----END PGP SIGNATURE-----
11:13 p.m.
New subject: XEmacs package of unreleased Gnus 5.10.7 (was: XEmacs Packages have been pre-released 2005-03-26-20)
On Sat, Mar 26 2005, Norbert Koch wrote:
Previously Announced Packages Still in Pre-Release:
gnus-1.84-pkg.tar.gz upstream version: 5.10.7
There is no upstream release "Gnus 5.10.7". I'm quite surprised that
the XEmacs team creates package releases from (work-in-progress) CVS
branches, even if this branch corresponds to the stable series.
To what date does it correspond? There have been quite important
commits on 2005-03-25 (sync of rfc2047.el from the trunk) in the v5-10
branch.
(I think that we should have a release of Gnus 5.10.7 within the next
few weeks, if Lars agrees.)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
11:43 p.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
* Reiner Steib <reinersteib+gmane(a)imap.cc> writes:
On Sat, Mar 26 2005, Norbert Koch wrote:
> Previously Announced Packages Still in Pre-Release:
> gnus-1.84-pkg.tar.gz upstream version: 5.10.7
There is no upstream release "Gnus 5.10.7".
It may not be "released" but it would be quite confusing to call it
5.10.6 in $AUTHOR_VERSION in the package Makefile while in gnus.el
there is:
,----
| (defconst gnus-version-number "5.10.7"
| "Version number for this version of Gnus.")
`----
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| I am Dyslexic of Borg. |
| Fusistance is retile. Your arse will be laminated. |
|------------------------------------<steve(a)sxemacs.org>---|
7:10 p.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
On Sun, Mar 27 2005, Steve Youngs wrote:
* Reiner Steib <reinersteib+gmane(a)imap.cc> writes:
> On Sat, Mar 26 2005, Norbert Koch wrote:
>> Previously Announced Packages Still in Pre-Release:
>> gnus-1.84-pkg.tar.gz upstream version: 5.10.7
> There is no upstream release "Gnus 5.10.7".
It may not be "released" but it would be quite confusing to call it
5.10.6 in $AUTHOR_VERSION in the package Makefile while in gnus.el
there is: [ (defconst gnus-version-number "5.10.7" ...) ]
The version numbers in Gnus CVS (traditionally?) correspond to the
next release. (People using versions directly from CVS usually know
what they are doing.)
It will also be confusing to tell users to "Upgrade to 5.10.7, this
bug is already fix there." when they already use something labeled
"5.10.7".
I don't know about XEmacs' policies for packages, but wouldn't it be
better and less confusing for everybody to ask Lars to release Gnus
5.10.7, say in a couple of weeks (May 1st?)? (There some minor
changes that should be done before the release: nnrss.el, refcard,
...)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
12:39 a.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
* Reiner Steib <reinersteib+gmane(a)imap.cc> writes:
On Sun, Mar 27 2005, Steve Youngs wrote:
> * Reiner Steib <reinersteib+gmane(a)imap.cc> writes:
> > There is no upstream release "Gnus 5.10.7".
> It may not be "released" but it would be quite
confusing to call
> it 5.10.6 in $AUTHOR_VERSION in the package Makefile while in
> gnus.el there is: [ (defconst gnus-version-number "5.10.7" ...) ]
The version numbers in Gnus CVS (traditionally?) correspond to the
next release.
IMO, Gnus should do something to differentiate between released and
unreleased versions.
(People using versions directly from CVS usually know what they
are doing.)
Indeed. So does the XEmacs Gnus package maintainer, although that
idiot seems to expend a lot of effort trying to disprove that. :-)
It will also be confusing to tell users to "Upgrade to 5.10.7,
this bug is already fix there." when they already use something
labeled "5.10.7".
There are a lot of pretty important and non-trivial fixes in the v5_10
Gnus CVS branch over and above 5.10.6. Fixes that I felt were
significant enough to warrant updating the XEmacs Gnus package.
And when there are more such changes (or 5.10.7 is "officially"
released) I'll update the XEmacs Gnus package again.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| I am Dyslexic of Borg. |
| Fusistance is retile. Your arse will be laminated. |
|------------------------------------<steve(a)sxemacs.org>---|
5:37 a.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
>>>> "SY" == Steve Youngs
<steve(a)sxemacs.org> writes:
SY> There are a lot of pretty important and non-trivial fixes in
SY> the v5_10 Gnus CVS branch over and above 5.10.6. Fixes that I
SY> felt were significant enough to warrant updating the XEmacs
SY> Gnus package.
Are you David Kastrup in drag? ;-)
SY> And when there are more such changes (or 5.10.7 is
SY> "officially" released) I'll update the XEmacs Gnus package
SY> again.
I think with Gnus it would make sense to have a "gnus" package and an
"ognus" ("ngnus", "mgnus", ...) package. It's a
harebrained idea, but
(I think) it might even be possible to simply install both packages
into the same place in any given package hierarchy.
This is entirely up to you and Norbert though, as it has the potential
to be a fair amount of extra work.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
10:43 a.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
* Stephen J Turnbull <stephen(a)xemacs.org> writes:
Are you David Kastrup in drag? ;-)
Not quite, but if you let me borrow your fish-net stockings, I'll be
set.:-P
I think with Gnus it would make sense to have a "gnus"
package and
an "ognus" ("ngnus", "mgnus", ...) package.
Oh, scary shit. Do you want to fend off the "Gnus ate my mail" and "I
tried ngnus and when I went back to gnus I couldn't find my mail"
FAQ's?
It's a harebrained idea, but (I think) it might even be possible
to simply install both packages into the same place in any given
package hierarchy.
You'd have to special case it otherwise gnus will go in lisp/gnus and ognus
will go in lisp/ognus (and that's too frightening to even contemplate).
Theoretically possible of course, but IMO development/beta/alpha packages
shouldn't be distributed by XEmacs.org. That's the role of upstream.
This is entirely up to you and Norbert though, as it has the
potential to be a fair amount of extra work.
Indeed. I can't say that I'm overly keen for this to become a
reality.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| I am Dyslexic of Borg. |
| Fusistance is retile. Your arse will be laminated. |
|------------------------------------<steve(a)sxemacs.org>---|
5:19 a.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
>>>> "SY" == Steve Youngs
<steve(a)sxemacs.org> writes:
> I think with Gnus it would make sense to have a "gnus"
package
> and an "ognus" ("ngnus", "mgnus", ...) package.
SY> Oh, scary shit.
Hey, the guy who's package maintainer for the MUA that's more complex
than any OS that actually works shouldn't be scared of a little admin
code, should he? ;-)
SY> Theoretically possible of course, but IMO
SY> development/beta/alpha packages shouldn't be distributed by
SY> XEmacs.org. That's the role of upstream.
That logic leads to reverting to 5.10.6 until 5.10.7 is officially
released. Give me back my fishnet stockings, and the pink lipstick
with sparkles, too!
SY> Fusistance is retile. Your arse will be laminated.
Your current .sig is even more than usually apprpriate in this
context!
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
9:10 a.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
On Tue, Apr 05 2005, Stephen J. Turnbull wrote:
>>>>> "SY" == Steve Youngs
<steve(a)sxemacs.org> writes:
Hey, the guy who's package maintainer for the MUA that's more complex
than any OS that actually works shouldn't be scared of a little admin
code, should he? ;-)
LOL
SY> Theoretically possible of course, but IMO
SY> development/beta/alpha packages shouldn't be distributed by
SY> XEmacs.org. That's the role of upstream.
That logic leads to reverting to 5.10.6 until 5.10.7 is officially
released.
FYI: Lars agreed to my suggestion of releasing 5.10.7 soon.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
1:43 p.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
>>>> "Reiner" == Reiner Steib
<reinersteib+gmane(a)imap.cc> writes:
Reiner> FYI: Lars agreed to my suggestion of releasing 5.10.7
Reiner> soon.
Cool! In that case, Steve got the timing exactly right, because it
won't need to get out of XEmacs pre-release before you guys do the
upstream release.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
7:56 a.m.
New subject: XEmacs package of unreleased Gnus 5.10.7
Reiner Steib <reinersteib+gmane(a)imap.cc> writes:
On Sun, Mar 27 2005, Steve Youngs wrote:
> * Reiner Steib <reinersteib+gmane(a)imap.cc> writes:
>
> > On Sat, Mar 26 2005, Norbert Koch wrote:
> >> Previously Announced Packages Still in Pre-Release:
> >> gnus-1.84-pkg.tar.gz upstream version: 5.10.7
>
> > There is no upstream release "Gnus 5.10.7".
>
> It may not be "released" but it would be quite confusing to call it
> 5.10.6 in $AUTHOR_VERSION in the package Makefile while in gnus.el
> there is: [ (defconst gnus-version-number "5.10.7" ...) ]
The version numbers in Gnus CVS (traditionally?) correspond to the
next release. (People using versions directly from CVS usually know
what they are doing.)
Hello Reiner, I can see your point, and differentiating released from
unreleased gnusae is definitely needed, I think.
For the XEmacs gnus package we would recommend to a certain XEmacs
package version, which is currently at:
gnus 1.84 The Gnus Newsreader and Mailreader.
This will avoid any confusion for people using the
PackageUserInterface.
It will also be confusing to tell users to "Upgrade to 5.10.7, this
bug is already fix there." when they already use something labeled
"5.10.7".
I don't know about XEmacs' policies for packages, but wouldn't it be
better and less confusing for everybody to ask Lars to release Gnus
5.10.7, say in a couple of weeks (May 1st?)? (There some minor
changes that should be done before the release: nnrss.el, refcard,
I'd rather ask to tack some indicator onto gnus-version for unreleased
code.
...)
Bye, Reiner.
Best regards,
Adrian
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
6955
days inactive
6965
days old
10 comments
5 participants
participants (5)
-
Adrian Aichner -
Norbert Koch -
Reiner Steib -
Stephen J. Turnbull -
Steve Youngs