issue-tracking | 11 May 05:37 2015

[Bug 165] Cannot generate configure script on FreeBSD

changed bug 165
What Removed Added
Status ASSIGNED RESOLVED
Resolution --- FIXED

Comment # 15 on bug 165 from This issue has been resolved with commit a41eac13d38be52266aa130c459f87b790990b19 today; which alters autogen.sh to reliably invoke the various autotools on FreeBSD. Time for tea and cake.
You are receiving this mail because:
  • You are the QA Contact for the bug.
Steve Youngs | 11 May 01:35 2015
X-Face
Face

Re: My Plan for early-packages (user packages)

[ Quoted in full because Nelson forgot to send it to the list :-) ]

Nelson Ferreira <nelson.ferreira <at> inware.org> writes:

  >> On May 10, 2015, at 0:56 , Steve Youngs <steve <at> sxemacs.org> wrote:
  >> 
  >> Hey Peeps!
  >> 
  >> Riding on the back of my XDG init directory change I want to allow an
  >> XDG compatible place for early-packages.
  >> 
  >> [...]
  >> 
  >> - If you use the legacy init directory (~/.sxemacs), no matter how
  >> you've convinced SXEmacs to use that, then these packages will go
  >> there.  IOW, nothing changes.
  >> 

  > Since we have --user-init-directory and we are splitting the possible location
  > of the user-package-directory I think it is only sensible to add 
  > --user-package-directory

OK, I'm not against this idea, but on the other hand I'm not overly sure
it'd be needed.  You can already set your package path at compile time
with `--with-package-path', and `--with-package-prefix'[1], or at run
time with $EMACSPACKAGEPATH.  Also, $SXE_USE_LEGACY would mean
early-packages go in ~/.sxemacs/

Personally, I don't like any of the `-user*' command line switches, but
not enough to go to the effort of removing them. :-)

  >> [...]
  >> One thing I am not going to do is support "cross-pollination".  If you
  >> want your init in ~/.sxemacs that's where you keep your packages as
  >> well.  If you want a XDG init, your packages will be in a XDG location
  >> too.
  >> 
  >> 

  > Well my request above is somewhat different since it is an override
  > through the command line.

I'm not going to say "yes" or "no" just yet, what I will say is that
I'll look at it and do my best to keep you happy. :-)

Footnotes: 
[1]  Admittedly, these are really for messing about with the system
     package directories, rather than the user ones.

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Steve Youngs | 10 May 06:56 2015
X-Face
Face

My Plan for early-packages (user packages)

Hey Peeps!

Riding on the back of my XDG init directory change I want to allow an
XDG compatible place for early-packages.

These packages should live in ${XDG_DATA_HOME}/sxemacs, That's
~/.local/share/sxemacs to the XDG-illiterate. :-)  Currently, they live
under `user-init-directory', for example, mine are in...

  (car early-packages)
  => "/home/steve/.config/sxemacs/site-packages/" [1]

OK, here is how I think it should work...

  - If you use the legacy init directory (~/.sxemacs), no matter how
    you've convinced SXEmacs to use that, then these packages will go
    there.  IOW, nothing changes.

  - All of us 21st century types who use the XDG init directory will
    keep our packages in ${XDG_DATA_HOME}/sxemacs

  - If you have packages in both locations (XDG and legacy) only one
    will be in the load-path, but it'll probably warn you.

The preferred defaults will be the XDG locations for both init directory
and user packages, XDG_CONFIG_HOME for init, and XDG_DATA_HOME for
packages.  What I mean by "preferred default" is that on a new user
setup that doesn't have any pre-existing SXEmacs directories you get the
XDG locations unless you jump through a hoop.[2]

One thing I am not going to do is support "cross-pollination".  If you
want your init in ~/.sxemacs that's where you keep your packages as
well.  If you want a XDG init, your packages will be in a XDG location
too.

Footnotes: 
[1]  early-packages can include sxemacs-packages, xemacs-packages, and
     mule-packages as well, but I only have some site-packages there.

[2]  That hoop could be `mkdir ~/.sxemacs', or setting $SXE_USE_LEGACY

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Steve Youngs | 10 May 04:43 2015
X-Face
Face

New Snapshot Available -- v22.1.15p132

*********************** N O T E ******************************

If you installed the previous snapshot you will need to delete
$prefix/share/sxemacs-22.1.15/lisp/site-start.el 

**************************************************************

Grab 'em while they're hot!

http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p132.tar.bz2
http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p132.tar.gz
http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p132.tar.lzma
http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p132.tar.xz

New in this snapshot
--------------------
  o No more horrible hackiness in a site-start.el

  o Consistent command line args.  Any -long-option now has a
    corresponding --long-option, and vice verse.

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
issue-tracking | 9 May 14:00 2015

[Bug 165] Cannot generate configure script on FreeBSD

Comment # 14 on bug 165 from I've disabled email to the guy who originally reported this because it now just bounces "account disabled"
You are receiving this mail because:
  • You are the QA Contact for the bug.
issue-tracking | 9 May 13:55 2015

[Bug 165] Cannot generate configure script on FreeBSD

changed bug 165
What Removed Added
CC horst <at> sxemacs.org, lsdhq <at> inbox.ru  

You are receiving this mail because:
  • You are the QA Contact for the bug.
issue-tracking | 9 May 13:12 2015

[Bug 165] Cannot generate configure script on FreeBSD

changed bug 165
What Removed Added
QA Contact   sxemacs-devel <at> sxemacs.org

Comment # 13 on bug 165 from Horst, buddy! You messaged me several weeks (months?) ago saying that you had autoconf-ish changes ready to go. I was kinda hoping that... a) They fixed this bug b) I'd see them. :-)
You are receiving this mail because:
  • You are the QA Contact for the bug.
Steve Youngs | 5 May 14:01 2015
X-Face
Face

A little apache help wanted.

Hey!

Do any of you guys know your way around apache?  What do I need to do so
that the file lists at http://downloads.sxemacs.org/releases/ and
http://downloads.sxemacs.org/snapshots/ (and the package directories)
are wide enough to see the entire filename?

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Steve Youngs | 5 May 13:54 2015
X-Face
Face

New Snapshot Tarballs Available!

Just in case you've forgotten your git-fu, I'm uploading a set of
snapshot tarballs that include the new XDG init directory stuff.

http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p129.tar.gz
http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p129.tar.bz2
http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p129.tar.lzma
http://downloads.sxemacs.org/snapshots/sxemacs-22.1.15p129.tar.xz

They'll probably be there by the time you read this.

And no, you don't have to use the XDG directory if you don't want to.
And no, you don't have to do anything at all to keep your set up as it
is now.  And no, SXEmacs will not try to migrate you to the new set up.

Have fun!

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Steve Youngs | 1 May 15:58 2015
X-Face
Face

XDG init directory

Hey!

I believe that the default value of `user-init-directory' should be
$XDG_CONFIG_HOME/sxemacs.  I also think that it'd be nice, if possible,
to allow people to continue to use ~/.sxemacs if they want to.

Enter beautiful code to keep everyone happy...

Attachment: application/emacs-lisp, 1229 bytes

Enter brick wall that I've hit...

user-init-directory is in startup.el which is dumped.  What is happening
is that the value for user-init-directory is being hard-coded to
whatever #'find-user-init-directory returns for the user building
SXEmacs at the time.  So much for the beautiful code to keep everyone
happy.

I don't know how to solve this problem.  Has anyone got any brilliant
ideas?  Maybe I've done something stupid and just can't see it (it has
been a while since I've touched any elisp).

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Christopher Turkel | 1 Jul 00:18 2014
Picon

xwem

I know this is a long, long shot but on Archlinux (Or Ubuntu 14.10) xwem fails to work with network error "connection refused". 

I tried it with startx -tcp-listen and nothing.

I realize that the chances of this working are slim but I thought I'd try.

Gmane