Tag Archives: fink

As before, this also affects distribution of updated package descriptions via the rsync mirrors. The following two workarounds are available:

Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.

Use a different rsync mirror. The following mirrors update directly from CVS and are not affected by the outage:rsync://ber.de.eu.finkmirrors.net/finkinfo/rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources. The following two workarounds are suggested:

Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged. This will have fink try to download from the original source first.

As before, this also affects distribution of updated package descriptions via the rsync mirrors. The following two workarounds are available:

Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.

Use a different rsync mirror. The following mirrors update directly from CVS and are not affected by the outage:rsync://ber.de.eu.finkmirrors.net/finkinfo/rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources. The following two workarounds are suggested:

Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged. This will have fink try to download from the original source first.

As before, this also affects distribution of updated package descriptions via the rsync mirrors. The following two workarounds are available:

Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.

Use a different rsync mirror. The following mirrors update directly from CVS and are not affected by the outage:rsync://ber.de.eu.finkmirrors.net/finkinfo/rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources. The following two workarounds are suggested:

Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged. This will have fink try to download from the original source first.

You may have noticed that http://www.finkproject.org is unavailable. The hosting provider at xs4all, where the machine is located, has been notified. We regret the inconvenience.

In addition to web services, this also affects distribution of updated package descriptions via the rsync mirrors. The following two workarounds are available:

Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.

Use a different rsync mirror. The following mirrors update directly from CVS and are not affected by the outage:rsync://ber.de.eu.finkmirrors.net/finkinfo/rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources. The following two workarounds are suggested:

Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged. This will have fink try to download from the original source first.

Fink’s xinitrc package provides similar functionality to X11 on 10.4 as is available on 10.5 and 10.6. It provides Fink packages with a straightforward way to have executables run automatically when X11 is started without modifying the system area, instead using scripts in /sw/etc/xinitrc.d (assuming a default fink setup). Moreover, when a package is removed, its script will also be removed. Currently, the following packages use it:

dbus

kinput2

uim

user-ja

xfontpath

xinitrc is used by these packages on 10.5 and later as well as 10.4. Since dbus is in the dependency chain for both GNOME and KDE, the behavior of xinitrc is important for users of those desktop environments.

Issues

xinitrc does have a side effect that needs to be taken into account. It is set up, deliberately, to circumvent the default script setup from 10.5 or 10.6’s X11 with its own, similar, setup, cf.:http://article.gmane.org/gmane.os.macosx.fink.devel/18879and its default setup doesn’t search $HOME.xinitrc.d for user scripts.
Fortunately, it’s straightforward to do so, and the method provides 10.4 users with the ability to set up scripts in $HOME/.xinitrc.d, too.

Also, if you’re using xinitrc because other Fink packages Depend on it, you may lose some functionality if you need to reinstall X11 (e.g. if you’re using Xquartz on 10.5). If so, then use

fink reinstall xinitrc

to restore it.

10.5 and 10.6

Basically, we just need a way to reactivate the existing handling of $HOME/.xinitrc.d . The xinitrc package provides a couple of system administrator entry points. Let’s use one which gets processed after the script files that are installed by fink packages. We can do this via the following steps:

The use of a $HOME/.xinitrc file to customize X11 has been deprecated as of OS 10.5. Unfortunately, due to time constraints, we haven’t set down in the documentation what users should be doing. I hope to set some ideas down here to clarify the situation.

The old way:

The presence of a $HOME/.xinitrc file replaces the system’s default X11 startup sequence. A couple of consequences are:

The user must make sure to run a window manager (unless one isn’t desired), e.g. just havingxterm
will generate an xterm with no window decorations, and any further X11 applications started from that xterm will be unmanaged. In this case the user probably wanted something likexterm &
quartz-wm

The user must make sure that $HOME/.xinitrc ends with a non-backgrounding command, or X11 will quit immediately. This would be the case in the prior example above if the user hadxterm &
quartz-wm &

The new way:

Instead of a single $HOME/.xinitrc file, under the current incarnation of Apple’s X11 (and any Xorg 7, really), one can do the following:

Create the directory $HOME/.xinitrc.d

For anything you want to run, create an executable shell script in that directory. For example, to run Fink’s xpad application on startup, create a $HOME/.xinitrc.d/xpad.sh (the name is somewhat arbitrary, but see below) with contents#!/bin/sh
/sw/bin/xpad

and make it executable via

chmod a+x $HOME/.xinitrc.d/xpad.sh

Note that in this case you don’t have to set a window manager.

The window manager can be changed in the same way. There is only one subtlety: the contents of $HOME/.xinitrc.d are run in the order that the filenames appear in a listing, and generally one will want the window manager to be run last, so its script should be named appropriately. For example, you could have 0-xpad.sh and 99-evilwm.sh scripts to run the evilwm window manager and start xpad automatically.

It’s easy to keep a list of scripts that start one item, and to set whether they get run or not by using

chmod a+x <name of script>.sh

or

chmod a-x <name of script>.sh

respectively.

Note: It’s slightly more complicated to set things up for GNOME or KDE, and I will discuss that issue in a subsequent entry.