Opened 9 years ago

Closed 5 years ago

#49619 closed defect (fixed)

no stable xemacs, no sumo package

Reported by: flabes@… Owned by: dstrubbe (David Strubbe)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: basmac
Port: xemacs

Description

The stable version 21.4.22 of XEmacs is gone, the only available version is 21.5.16_0, which is beta.

With this version, I have two problems:

  • minor: it conflicts with the ctags port, but I can overcome this with forcing the installation
  • major: packages from the sumo tar ball are not found: for example, the file vc.el from the VC package is installed in /opt/local/lib/xemacs-21.5.16/xemacs-packages/lisp/vc/vc.el, while the load-path variable is set to ("/opt/local/lib/xemacs-21.5-b16/lisp/mule/" "/opt/local/lib/xemacs-21.5-b16/lisp/"); http://www.xemacs.org/Documentation/packageGuide.html#The_Sumo_Tarball suggests to use (for 21.5) yet another location: "in recent beta XEmacs (since about 21.5) both regular and MULE packages should be untarred in $prefix/share/xemacs/xemacs-packages and $prefix/share/xemacs/mule-packages, respectively."

Is there any chance to get the stable version 21.4.22 back? I'm not sure whether the sumo tar ball requires a 21.4 XEmacs.

BTW: why did you pick 21.5.16 while the latest beta is 21.5.33 from 2013-01-04?

Change History (13)

comment:1 Changed 9 years ago by flabes@…

Probably related to #19833.

comment:2 Changed 9 years ago by dstrubbe (David Strubbe)

Cc: dstrubbe@… added

Cc Me!

comment:3 Changed 9 years ago by dstrubbe (David Strubbe)

You can always go back to a previously installed version if you are having trouble with a newer one: e.g. 'port activate xemacs @21.4.22'. That version is not 'gone'.

Force-installing given the conflict with ctags may have caused problems -- I wouldn't do that unless you have investigated why they conflict and are sure it is ok.

Do you have any reason to think the sumo version would require XEmacs 21.4? If it does, since it is the latest sumo on the XEmacs website, then it is hard to imagine how they expect 21.5 to be usable.

I was not able to figure out how to get version 21.5.33 to build properly. That is why I updated it to 21.5.16.

comment:4 Changed 9 years ago by dstrubbe (David Strubbe)

ctags conflict fixed in r142233.

comment:5 in reply to:  4 Changed 9 years ago by EJFielding (Eric Fielding)

Replying to dstrubbe@…:

ctags conflict fixed in r142233.

I ran "port upgrade outdated" last week and it failed on the xemacs step, so I added "and not xemacs" to complete the upgrade. Now I ran it again, and the ctags port said it could not activate the latest version because xemacs is using an older version. How do we tell which version of ctags works with which version of xemacs?

Or do we just do the "port upgrade outdated" twice?

I tried deactivating the active xemacs @21.4.22_10 and re-ran "port upgrade outdated", but it seems to have skipped both ctags and xemacs.

Last edited 9 years ago by EJFielding (Eric Fielding) (previous) (diff)

comment:6 Changed 9 years ago by dstrubbe (David Strubbe)

In general, any port is only expected to work with the current version of its dependents. So, you need to upgrade both ctags and xemacs. Do 'port clean xemacs ctags' certainly to be sure you don't have something leftover from before this update. When you deactivate xemacs, it will not be updated. But, that may be what you need to do in this case. While xemacs is deactivated, update ctags. Then update xemacs.

comment:7 in reply to:  6 Changed 9 years ago by EJFielding (Eric Fielding)

Replying to dstrubbe@…:

In general, any port is only expected to work with the current version of its dependents. So, you need to upgrade both ctags and xemacs. Do 'port clean xemacs ctags' certainly to be sure you don't have something leftover from before this update. When you deactivate xemacs, it will not be updated. But, that may be what you need to do in this case. While xemacs is deactivated, update ctags. Then update xemacs.

Thanks for the explanation! This worked great. Thanks also for fixing the port!

comment:8 Changed 9 years ago by dstrubbe (David Strubbe)

Does this solve the sumo location issue? I don't know how to check whether the packages are being found or not.

===================================================================
--- Portfile    (revision 142463)
+++ Portfile    (working copy)
@@ -72,12 +72,12 @@
 
 destroot.keepdirs ${destroot}${prefix}/lib/xemacs
 post-destroot {
-    set xemacs_lib ${destroot}${prefix}/lib/xemacs-${version}
+    set xemacs_lib ${destroot}${prefix}/share/xemacs
     xinstall -d -m 0755 ${xemacs_lib}
-    system "cd ${destroot}${prefix}/lib && ln -s xemacs-${version} xemacs"
+    system "cd ${destroot}${prefix}/share && ln -s xemacs-${version} xemacs"
     if {[file exists ${workpath}/mule-packages]} {
         ui_debug "Installing mule-sumo distribution into destroot"
-        file copy ${workpath}/mule-packages ${xemacs_lib}/
+        file copy ${workpath}/mule-packages ${xemacs_lib}
     }
     if {[file exists ${workpath}/xemacs-packages]} {
         ui_debug "Installing sumo distribution into destroot"

comment:9 Changed 9 years ago by basmac

Cc: barry.j.mcinnes@… added

Cc Me!

comment:10 in reply to:  description Changed 9 years ago by basmac

The beta version installs but fails to run, the stable version does not install it goes and installs the beta version, for us on 10.10 all latest versions.

comment:11 Changed 9 years ago by dstrubbe (David Strubbe)

Just to be clear: there is only ever one version of any port available. So, no you cannot install the previous version (which is the stable version).

comment:12 Changed 6 years ago by jmroot (Joshua Root)

Cc: dstrubbe removed
Owner: changed from macports-tickets@… to dstrubbe
Status: newassigned

comment:13 Changed 5 years ago by dstrubbe (David Strubbe)

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.