Re: Wanting to upload 2 new packages
On 12/31/2011 08:14 AM, Stephen J. Turnbull wrote:
steven Mitchell writes:
> One is buffer-colors.el, a package that involves an easy method for
> changing buffer colors on the fly,
What are "buffer colors"? Do you mean background and foreground
colors of the default face?
Yes, that is correct.
> We were thinking it might go in edit-utils package--what do
you
> think?
Seems reasonable.
> The second file is icon-themes.el, a package to change icons as a
> "set" in the XEmacs menu bar.
"Menu bar"? Do you mean the toolbar? The menubar doesn't normally
sport icons AFAIK, I don't even know if it supports them.
Oops, I did indeed
mean the toolbar.
I think that one can go in edit-utils as well.
> text icons
> Oxygen (from KDE)
> Open Icon Library
> Tango Icons
> default icons that come with XEmacs
Are these GPL-compatible (either under the GPL or under a license that
that is freer in all respects than the GPL)? If not, I don't think we
should include them in the same package. To avoid GPL encumbrance,
they should be distributed in a separate package as a "convenience to
users", not as part of our distribution. As long as it's a verbatim
distribution (which makes sense for icons), the "mere aggregation"
clause clearly covers us.
I put a text file, sources.txt, in each icon directory
and it lists the
names of the icons
and the place I got them from and the license. The three sources for
the icons were
mentioned as desirable (as far as I remember) on xemacs-beta about 6
months ago or so.
Tango was fine, public domain
Oxygen icons are LGPL
Open Icon Library was a problem as the whole collection was not released
under a
single license--they have icons with 7 licenses, but they sort them by
licenses each in separate
directories in the devel tar.gz on their site. Just to make things
interesting, they have
many of icons listed as having dual licenses. As good-looking as some
of the icons are, we stuck
to just those we new the license would be Ok (I think). The text icons
are created by making a glyph in
XEmacs with the 'string option, so we figure that is covered as GPL3 or
later, same as the notice
we put in the icon-themes.el file. The 5th set was the default icons
from XEmacs, so users can put
everything back to normal. I have other ideas, but that is all that is
implemented now.
I am not an expert in licenses, so if I made a mistake, I will find new
icons and repair the themes.
> The second question is, once we figure out where to upload
them,
> who do we ask for permission to upload them at that place (or
> places)?
Mike Sperber<mike(a)xemacs.org>. You need to get (a) bitbucket
account(s) and commit access to the relevant packages, then add the
new files, commit, and push. Then send mail to Norbert Koch
<viteno(a)xemacs.org>, who actually creates the tarballs and uploads
them to the FTP/HTTP host. I'm not sure what to do about non-GPL icon
themes; they'll have to wait.
OK I will email Mike Sperber.
I have a bitbucket account and have fixed the ssh key problem.
We uploaded the xpm-mode a few days ago, but I didn't know to send an
email to
Norbert Koch. I'll do that too.
The problem with the ssh key was including just enough of the file.
the ssh public key file was 5 pieces:
header at the top (ssh, etc)
a single space
the key
a single space
a user:domain
First tried to copy/paste just the key, and then the whole
thing--neither worked.
then copy/pasted the header, single space, the key, leaving off the
second single space and
the user-domain statement. That worked.
Just mentioning what worked in case someone else has trouble, maybe it
will help them.
Thank you for the help.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta