From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.help Subject: Re: w3m-el-snapshot installation Date: Sun, 27 Mar 2011 18:00:50 +0200 Message-ID: <87fwq8wo25.fsf@web.de> References: <8739mc3830.fsf@engels.HistoricalMaterialism.info> <87y64212kz.fsf@engels.HistoricalMaterialism.info> <87tyep1m3m.fsf@engels.HistoricalMaterialism.info> <87pqpc21px.fsf@engels.HistoricalMaterialism.info> Reply-To: michael_heerdegen@web.de NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1301241722 11404 80.91.229.12 (27 Mar 2011 16:02:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 27 Mar 2011 16:02:02 +0000 (UTC) To: Emacs mailing list Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Mar 27 18:01:58 2011 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Q3sPd-0007qW-IS for geh-help-gnu-emacs@m.gmane.org; Sun, 27 Mar 2011 18:01:57 +0200 Original-Received: from localhost ([127.0.0.1]:36033 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q3sPc-0008LJ-4q for geh-help-gnu-emacs@m.gmane.org; Sun, 27 Mar 2011 12:01:56 -0400 Original-Received: from [140.186.70.92] (port=35524 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q3sNk-0008Io-8i for help-gnu-emacs@gnu.org; Sun, 27 Mar 2011 12:00:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q3sNj-0005kV-1R for help-gnu-emacs@gnu.org; Sun, 27 Mar 2011 12:00:00 -0400 Original-Received: from fmmailgate02.web.de ([217.72.192.227]:44599) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q3sNi-0005k5-Js for help-gnu-emacs@gnu.org; Sun, 27 Mar 2011 11:59:59 -0400 Original-Received: from smtp08.web.de ( [172.20.5.216]) by fmmailgate02.web.de (Postfix) with ESMTP id 238C819B26CBB for ; Sun, 27 Mar 2011 17:59:57 +0200 (CEST) Original-Received: from [89.204.153.231] (helo=snow) by smtp08.web.de with asmtp (WEB.DE 4.110 #2) id 1Q3sNg-00049c-00 for help-gnu-emacs@gnu.org; Sun, 27 Mar 2011 17:59:56 +0200 In-Reply-To: <87pqpc21px.fsf@engels.HistoricalMaterialism.info> (Haines Brown's message of "Sun, 27 Mar 2011 08:21:30 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Sender: michael_heerdegen@web.de X-Provags-ID: V01U2FsdGVkX1+nY7tM/ucbAANLHsE6oX7UM5poTQkOewelTnIb bXeMXZts+70q3Re3neJiuDsY4tg+Q9J0gAglCX+8IWOS1RMTRq Jl77jqSlDT+ePuSTTurQ== X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4-2.6 X-Received-From: 217.72.192.227 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:80471 Archived-At: Haines, > > /usr/lib/emacsen-common/packages/install/w3m-el-snapshot emacs23 > > Michael, yes, the output was indeed interesting: > > First, nothing happens > > $ /usr/lib/emacsen-common/packages/install/w3m-el-snapshot emacs23 > $ > > If I try without the "emacs23" appended, I get: > > $ /usr/lib/emacsen-common/packages/install/w3m-el-snapshot > install/w3m-el-snapshot: byte-compiling for , logged in > /tmp/elc.6XlCZFi50OXr > mkdir: cannot create directory `/usr/share//site-lisp/w3m': No such file > or directory > > Given the innards of w3m-el-snapshot, this is what I'd expect, for the > value used to construct the path is null. However, it does show that the > executable script is at least trying. Since the first thing it does is > to create the w3m directory, which doesn't happen, there seems to be a > pothole in the following script: > > ... > FLAVOR=$1 > ... > ELCDIR=/usr/share/$FLAVOR/site-lisp/$PKGSNAME > ... > if [ ! -d "$ELCDIR" ]; then > mkdir "$ELCDIR" > chmod 755 "$ELCDIR" > fi I don't think that. The installation script needs to get an Emacs flavor (like "emacs23") as the first argument. If this first arg is void, mkdir complains because it tries to create "w3m" under "/usr/share//site-lisp", which doesn't exist. But if you don't get any output running $ /usr/lib/emacsen-common/packages/install/w3m-el-snapshot emacs23 I guess the only possible case is that the script exits here: case $FLAVOR in emacs2[3-9]|emacs-*|emacs*cvs*) if [ -f "$ELDIR/w3m-e21.el" ] && [ ! -f "$ELDIR/w3m-e23.el" ]; then exit 0 fi ;; esac That means that you would have a directory "/usr/share/emacs23/site-lisp/w3m-e21.el" on your system. If that's true, we must get rid of it. Do you have it? > I don't know how to debug to see whether in fact $FLAVOR and $PKGSNAME > are created as the script runs. However, I don't see how the value of > $PKGSNAME gets defined, for the line above, which is its first > appearance of this variable in the script, it is used to build the value > of ELCDIR. Is this why the path used to constuct the w3m directory ends > up with a null gap? PKGSNAME is defined in line 6 of the script: PKGSNAME=w3m The problem in your (illegal) call is the void FLAVOR variable. > However, I'm ignorant about such things and I apologize for the > speculation. In fact, I didn't even know emacs had a packages directory > where packages could be added or removed at will. Most things we discussed here only apply to the Debian Emacs installation. Other systems may have completely other directories etc. It is not a good idea to manually copy files to these directories. If you want to have a look behind the scenes, then you may visit the "w3m-el-snapshot_1.4.400+0.20100725-1_all.deb" package file with Emacs. (You can download it here: "http://packages.debian.org/squeeze/all/w3m-el-snapshot/download") If you have installed debian-el, you'll see which files it installs, and the scripts that are run when installing, removing etc. (Besides: You may consider to upgrade to Debian testing. I think stable primarily aims at servers, it has very out of date software. testing is also very "stable" and probably the better choice for daily usage. Michael.