Stephen J. Turnbull wrote:
Andreas Roehler writes:
> Maybe we could have a transition-archiv with all GPLv3 files so far in it.
> Then people could go on, as soon the matter arrived there.
> Too we could upload/adapt new things meanwhile.
But what good does that do if it doesn't run? Specifically, upload/
adapt without testing at all is kind of silly, isn't it? It just
sounds like extra work to me.
The point is that *you* can combine free software any way you like in
the privacy of your own machine. If you want to use GPLv3 code in
your personal version of XEmacs, there is no problem whatsoever.
So I may test v3 code and upload after testing onto the transition archiv.
Case is epa.el, wherefrom was said at comp.emacs.xemacs from, Fri,
24 Apr 2009 20:57:31 -0700, Message-ID: <m3d4b15qs4.fsf(a)127.0.0.1>
Epa seems to
remember the password for each XEmacs session, which for me means between
reboots and I only reboot when there's a new Fedora kernel out there,
sometimes even longer.
Epa has a couple other problems. First one is that it puts the cursor at
point-max, i.e. the end of the file. Quit silly. The other, much more
serious, is that it creates recovery files (i.e. #...# files) in PLAIN
text!! Not good.
Didn't remark that with latest GNU Emacs' epa, so I would check that with XEamcs.
you have GPLv3 code in your private hg repository, it doesn't
you can still sync *from* the GPLv2 XEmacs "official" repository to
your private repository. You just can't distribute your version of
XEmacs with your new code until it's fully GPLv3, specifically you
can't push to the public XEmacs repository.
XEmacs-Beta mailing list