-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL.html
641 lines (574 loc) · 27.1 KB
/
INSTALL.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<!--
Generated from $Fink: install.xml,v 1.49 2015/10/04 00:00:05 alexkhansen Exp $
-->
<title>Fink Documentation - Fink 0.41.1 Installation</title></head><body><h1 style="text-align: center;">Fink 0.41.1 Installation</h1>
<p>
These are the installation instructions for the "source" distribution
based on <tt style="white-space: nowrap;">fink-0.41.1</tt>, intended for use with OS X v.10.9 and later.</p>
<p>
This document does not apply to the "<a href="/download/index.php">binary</a>" distribution.
</p>
<p>
There are instructions for both first time installation and upgrading
from a previous version.
Fast track instructions for the impatient are at the top.
</p>
<h2>Contents</h2><ul><li><a href="#install-fast"><b>1 The Fast Track</b></a><ul><li><a href="#install-fast.req">1.1 Requirements</a></li><li><a href="#install-fast.scripted-install">1.2 First Time Installation Very Fast
Track</a></li><li><a href="#install-fast.install">1.3 First Time Installation Fast
Track</a></li></ul></li><li><a href="#install-first"><b>2 First Time Installation</b></a><ul><li><a href="#install-first.req">2.1 Requirements</a></li><li><a href="#install-first.directory">2.2 Choosing A Directory</a></li><li><a href="#install-first.install">2.3 Installation</a></li><li><a href="#install-first.x11">2.4 Getting X11 Sorted Out</a></li></ul></li><li><a href="#install-up03"><b>3 Upgrading Fink</b></a><ul><li><a href="#install-up03.packman">3.1 Updating The Package Manager</a></li><li><a href="#install-up03.update-all">3.2 Updating Packages</a></li></ul></li><li><a href="#install-up02"><b>4 Clean Upgrade</b></a><ul><li><a href="#install-up02.cleaninst">4.1 Situations Calling for a Clean Reinstall</a></li><li><a href="#install-up02.backup">4.2 Backing up to save time</a></li><li><a href="#install-up02.removing">4.3 Removing Your Old Fink</a></li><li><a href="#install-up02.reinstalling">4.4 Installing Fink Again</a></li></ul></li></ul><h2><a name="install-fast">1 The Fast Track</a></h2>
<p>
This section is for the impatient who don't want to take the time to
learn their way around the command line world and don't care that they
don't know what they're actually doing.
</p>
<p>
If you're looking for the real instructions, skip to the <a href="#install-first">next section</a>.
(You can still use this section as an example.)
</p>
<h3><a name="install-fast.req">1.1 Requirements</a></h3>
<p>
You need:
</p>
<ul>
<li><p>
An installed Mac OS X system, version 10.9 or later.
</p></li>
<li><p>
The Xcode Command Line Tools are mandatory. This package can be installed either by
downloading it directly via developer.apple.com, or by running the</p>
<pre>xcode-select --install</pre>
<p>command and choosing the
<b>Install</b> button in the window that pops up.
You may also need to use this command to update the tools,
especially if you're having build problems.</p>
<p>If you're doing a manual download, make sure that the tools you install match your
OS X version as well as your Xcode app version (if that is present).</p>
<p>You will need to accept the Xcode license as root. To do that, run</p>
<pre>sudo xcodebuild -license</pre>
<p>then scroll to the bottom of the text and type</p>
<pre>agree</pre>
<p>Some packages require the full Xcode.</p>
</li>
<li><p>Java. Entering</p>
<pre>javac</pre>
<p>from a Terminal.app window should suffice to make the system download it for you.</p></li>
<li><p>
Many other things that come with Mac OS X.
This includes perl and curl.
</p></li>
<li><p>
Internet access.
All source code is downloaded from mirror sites.
</p></li>
<li><p>
Patience.
Compiling several big packages takes time.
I'm talking hours or even days here.
</p></li>
</ul>
<h3><a name="install-fast.scripted-install">1.2 First Time Installation Very Fast
Track</a></h3>
<p>
Download the <a href="https://raw.githubusercontent.com/fink/scripts/master/srcinstaller/Install%20Fink.tool">
Install Fink.tool</a> script and double-click on it. This will automate the downloads
in the steps below.
</p>
<p>
The script may have to stop for you to do something. If so, run it again.
</p>
<h3><a name="install-fast.install">1.3 First Time Installation Fast
Track</a></h3>
<p>
Start out by copying the <tt style="white-space: nowrap;">fink-0.41.1.tar.gz</tt>
file to your home folder (it might also show up as <tt style="white-space: nowrap;">fink-0.41.1.tar</tt> if you
used Safari to download it).
Then, open Terminal.app and follow the session below.
Computer output is in <tt style="white-space: nowrap;">normal face</tt>, your input is in
<tt style="white-space: nowrap;"><b>bold face</b></tt> (or otherwise highlighted).
The actual input prompts from the shell may vary, and some chunks of
the output have been omitted (<tt style="white-space: nowrap;">...</tt>).
</p>
<p>Note: after you start the install process you may see
dialog windows asking whether you want to install XQuartz.
If you want to do so, go ahead. You won't have to stop the Fink install
to do that.</p>
<pre>[frodo:~] testuser% <b>tar xf fink-0.41.1.tar.gz</b>
[frodo:~] testuser% <b>cd fink-0.41.1</b>
[frodo:~/fink-0.41.1] testuser% <b>./bootstrap</b>
Fink must be installed and run with superuser (root) privileges
...
Choose a method: [1] <b>1</b>
sudo /Users/testuser/fink-0.41.1/bootstrap .sudo '/sw'
Password: <b>(your normal password here)</b>
...
OK, I'll ask you some questions and update the configuration file in
'/sw/etc/fink.conf'.
In what additional directory should Fink look for downloaded tarballs? [] <b>(press return)</b>
Which directory should Fink use to build packages? (If you don't know what this
means, it is safe to leave it at its default.) [] <b>(press return)</b>
"Fink can set the UID and GID of its build user dynamically...
...Allow Fink to set the UID/GID dynamically? [Y] <b>(press return)</b>
(1) Quiet (do not show download statistics)
(2) Low (do not show tarballs being expanded)
(3) Medium (will show almost everything)
(4) High (will show everything)
How verbose should Fink be? [2] <b>(press return)</b>
Proxy/Firewall settings
Enter the URL of the HTTP proxy to use, or 'none' for no proxy. The URL
should start with http:// and may contain username, password or port
specifications. [none] <b>(press return)</b>
Enter the URL of the proxy to use for FTP, or 'none' for no proxy. The URL
should start with http:// and may contain username, password or port
specifications. [none] <b>(press return)</b>
Use passive mode FTP transfers (to get through a firewall)? [Y/n] <b>(press return)</b>
Enter the maximum number of simultaneous build jobs.
...
Maximum number of simultaneous build jobs: [<number of cpus>] <b>(press return)</b>
Mirror selection
Choose a continent:
...
<b>(enter the numbers corresponding to your location)</b>
...
Writing updated configuration to '/sw/etc/fink.conf'...
Bootstrapping a base system via /sw/bootstrap.
...
<b>(take a coffee break while Fink downloads and compiles the base packages)</b>
...
You should now have a working Fink installation in '/sw'.
[frodo:~/fink-0.41.1] testuser% <b>cd</b>
[frodo:~] testuser% <b>rm -r fink-0.41.1</b>
[frodo:~] testuser% <b>/sw/bin/pathsetup.sh</b></pre>
<p>
The last command runs a little script to help set up your Unix paths
(and other things) for use with Fink. In most cases, it will run
automatically, and prompt you for permission to make changes. If
the script fails, you'll have to do things by hand (see below).
</p>
<p>
(If you need to do things by hand, and you are using csh or tcsh,
you need to make sure that the command
<tt style="white-space: nowrap;">source /sw/bin/init.csh</tt> is executed during startup of
your shell, either by .login, .cshrc, .tcshrc, or something else
appropriate. If you are using bash or similar shells, the command
you need is <tt style="white-space: nowrap;">. /sw/bin/init.sh</tt>, and places where it
might get executed include .bashrc and .profile.)
</p>
<p>
Once you have set up the paths, open a new Terminal.app window, and close
all other ones.
That's it, you now have a base Fink system installed.
</p>
<p>
Before you can install additional packages, you will need to download their
descriptions. To do this, in your new Terminal.app window, ether use:</p>
<pre>[frodo:~] testuser% <b>fink selfupdate-rsync</b>
Password: <b>(your normal password here)</b>
Please note: the simple command 'fink selfupdate' should be used for routine
updating; you only need to use a command like 'fink selfupdate-cvs' or 'fink
selfupdate --method=rsync' if you are changing your update method.
...
<b>(wait for the downloads to finish)</b></pre>
<p> (preferred) or</p>
<pre>[frodo:~] testuser% <b>fink selfupdate-cvs</b>
Password: <b>(your normal password here)</b>
Please note: the simple command 'fink selfupdate' should be used for routine
updating; you only need to use a command like 'fink selfupdate-cvs' or 'fink
selfupdate --method=rsync' if you are changing your update method.
fink is setting your default update method to cvs
Fink has the capability to run the CVS commands as a normal user. That has some
advantages - it uses that user's CVS settings files and allows the package
descriptions to be edited and updated without becoming root. Please specify the
user login name that should be used: [<your username>] <b>(press return)</b>
For Fink developers only: Enter your SourceForge login name to set up full CVS
access. Other users, just press return to set up anonymous read-only access.
[anonymous] <b>(press return)</b>
Checking to see if we can use hard links to merge the existing tree. Please
ignore errors on the next few lines.
Now logging into the CVS server. When CVS asks you for a password, just press
return (i.e. the password is empty).
/usr/bin/su hansen -c 'cvs -d":pserver:anonymous@fink.cvs.sourceforge.net:/cvsroot/fink" login'
Logging in to :pserver:anonymous@fink.cvs.sourceforge.net:2401/cvsroot/fink
CVS password: <b>(press return)</b>
Logging in to :pserver:anonymous@fink.cvs.sourceforge.net:2401/cvsroot/fink
...
<b>(wait for the downloads to finish)</b></pre>
<p>
especially if you are using a proxy.
</p>
<p>
You can now install packages with the <tt style="white-space: nowrap;">fink</tt>
command, like this:
</p>
<pre>[frodo:~] testuser% <b>fink install gimp2</b>
Password:
Scanning package description files..........
Information about 6230 packages read in 1 seconds.
fink needs help picking an alternative to satisfy a virtual dependency. The
candidates:
(1) db51-aes: Berkeley DB embedded database - crypto
(2) db51: Berkeley DB embedded database - non crypto
Pick one: [1]
The following package will be installed or updated:
gimp2
The following 308 additional packages will be installed:
aalib aalib-bin aalib-shlibs asciidoc atk1 atk1-shlibs autoconf2.6
automake1.11 automake1.11-core blt-dev blt-shlibs boost1.46.1.cmake
boost1.46.1.cmake-shlibs cairo cairo-shlibs celt-dev celt-shlibs cmake
cpan-meta-pm5124 cpan-meta-requirements-pm5124 cpan-meta-yaml-pm
cyrus-sasl2-dev cyrus-sasl2-shlibs daemonic db51-aes db51-aes-shlibs db53-aes
db53-aes-shlibs dbus dbus-glib1.2-dev dbus-glib1.2-shlibs dbus1.3-dev
dbus1.3-shlibs dirac-dev dirac-shlibs docbook-bundle docbook-dsssl-ldp
docbook-dsssl-nwalsh docbook-dtd docbook-xsl doxygen expat1 expat1-shlibs
exporter-pm extutils-cbuilder-pm extutils-command-pm extutils-install-pm
extutils-makemaker-pm extutils-makemaker-pm5124 extutils-manifest-pm
file-copy-recursive-pm file-temp-pm5124 fink-package-precedence flag-sort
fltk-x11 fltk-x11-shlibs fontconfig-config fontconfig2-dev fontconfig2-shlibs
freeglut freeglut-shlibs freetype219 freetype219-shlibs gawk gconf2-dev
gconf2-shlibs gd2 gd2-bin gd2-shlibs gdbm3 gdbm3-shlibs getoptbin
gettext-tools ghostscript ghostscript-fonts giflib giflib-bin giflib-shlibs
gimp2-shlibs glib2-dev glib2-shlibs glitz glitz-shlibs gmp5 gmp5-shlibs
gnome-doc-utils gnutls-2.12 gnutls-2.12-shlibs graphviz graphviz-shlibs grep
gtk+2 gtk+2-dev gtk+2-shlibs gtk-doc gtkglext1 gtkglext1-shlibs gts75
gts75-shlibs guile18 guile18-dev guile18-libs guile18-shlibs ilmbase
ilmbase-shlibs intltool40 iso-codes jack-dev jack-shlibs json-pp-pm lame-dev
lame-shlibs lcms lcms-shlibs libavcodec52-shlibs libavformat52-shlibs
libavutil50-shlibs libbabl0.1.0-dev libbabl0.1.0-shlibs libbonobo2
libbonobo2-dev libbonobo2-shlibs libcelt0.2-dev libcelt0.2-shlibs libcroco3
libcroco3-shlibs libdatrie1 libdatrie1-shlibs libexif12 libexif12-shlibs
libflac8 libflac8-dev libgcrypt libgcrypt-shlibs libgegl0.1.0-dev
libgegl0.1.0-shlibs libgettext3-dev libgettext3-shlibs libgettextpo2-dev
libgettextpo2-shlibs libglade2 libglade2-shlibs libgmpxx5-shlibs libgpg-error
libgpg-error-shlibs libgsf1.114-dev libgsf1.114-shlibs libgsm1-dev
libgsm1-shlibs libhogweed-shlibs libidl2 libidl2-shlibs libidn libidn-shlibs
libjasper.1 libjasper.1-shlibs libjpeg libjpeg-bin libjpeg-shlibs libjpeg8
libjpeg8-shlibs liblzma5 liblzma5-shlibs libming1-dev libming1-shlibs libmng2
libmng2-shlibs libncursesw5 libncursesw5-shlibs libogg libogg-shlibs
liboil-0.3 liboil-0.3-shlibs libopencore-amr0 libopencore-amr0-shlibs
libopenexr6-shlibs libopenjpeg libopenjpeg-shlibs libopenraw1-dev
libopenraw1-shlibs libpaper1-dev libpaper1-shlibs libpcre1 libpcre1-shlibs
libpng14 libpng14-shlibs libpng15 libpng15-shlibs libpng3 libpng3-shlibs
librarian.08-shlibs librsvg2 librsvg2-shlibs libschroedinger
libschroedinger-shlibs libsigsegv2 libsigsegv2-shlibs libsndfile1-dev
libsndfile1-shlibs libsoup2.4.1-ssl libsoup2.4.1-ssl-shlibs libspeex1
libspeex1-shlibs libspiro0 libspiro0-shlibs libtasn1-3 libtasn1-3-shlibs
libthai libthai-dev libthai-shlibs libtheora0 libtheora0-shlibs
libtheoradec1-shlibs libtheoraenc1-shlibs libtiff libtiff-bin libtiff-shlibs
libtool2 libtool2-shlibs libvorbis0 libvorbis0-shlibs libvpx libwmf
libwmf-shlibs libx264-115-dev libx264-115-shlibs libxml2 libxml2-bin
libxml2-py27 libxml2-shlibs libxslt libxslt-bin libxslt-shlibs lua51 lua51-dev
lua51-shlibs lynx m4 nasm netpbm10 netpbm10-shlibs nettle4a nettle4a-shlibs
ocaml openexr openexr-dev openjade openldap24-dev openldap24-shlibs opensp-bin
opensp5-dev opensp5-shlibs openssl100-dev openssl100-shlibs orbit2 orbit2-dev
orbit2-shlibs pango1-xft2-ft219 pango1-xft2-ft219-dev pango1-xft2-ft219-shlibs
parse-cpan-meta-pm passwd-core passwd-messagebus pixman pixman-shlibs
pkgconfig poppler-data poppler4 poppler4-glib poppler4-glib-shlibs
poppler4-shlibs popt popt-shlibs python27 python27-shlibs rarian rarian-compat
readline5 readline5-shlibs readline6 readline6-shlibs sdl sdl-shlibs
sgml-entities-iso8879 shared-mime-info sqlite3-dev sqlite3-shlibs swig
system-openssl-dev tcltk tcltk-dev tcltk-shlibs test-harness-pm5124
test-simple-pm5124 texi2html texinfo version-pm5124
version-requirements-pm5124 xdg-base xft2-dev xft2-shlibs xinitrc
xml-parser-pm5124 xmlto xvidcore xvidcore-shlibs xz yasm
The following 2 packages might be temporarily removed:
lcms tcltk-dev
Do you want to continue? [Y/n]
...</pre>
<p>
If these instructions don't work for you, well, you'll have to take
the time to read through the rest of this document and the <a href="/faq/">online FAQ</a>.
You can also ask on the <a href="/lists/fink-users.php">fink-users
mailing list</a>, but expect to be pointed back at the
documentation when your problem actually is well-documented.
</p>
<h2><a name="install-first">2 First Time Installation</a></h2>
<h3><a name="install-first.req">2.1 Requirements</a></h3>
<p>
You need:
</p>
<ul>
<li><p>
An installed Mac OS X system, version 10.9 or later.
</p></li>
<li><p>
The Xcode Command Line Tools are mandatory. This package can be installed either by
downloading it directly via developer.apple.com, or by running the</p>
<pre>xcode-select --install</pre>
<p>command and choosing the
<b>Install</b> button in the window that pops up, or you can install the full
Xcode if you prefer. You may also need to use this command to update the tools,
especially if you're having build problems.</p>
<p>If you're doing a manual download, make sure that the tools you install match your
OS X version as well as your Xcode app version (if that is present).</p>
<p>You will need to accept the Xcode license as root. To do that, run</p>
<pre>sudo xcodebuild -license</pre>
<p>then scroll to the bottom of the text and type</p>
<pre>agree</pre>q
<p>Some packages require the full Xcode.</p>
</li>
<li><p>Java. Entering</p>
<pre>javac</pre>
<p>from a Terminal.app window should suffice to make the system download it for you.</p></li>
<li><p>
Many other things that come with Mac OS X and the Developer Tools.
This includes perl and curl.
</p></li>
<li><p>
Internet access.
All source code is downloaded from mirror sites.
</p></li>
<li><p>
Patience.
Compiling several big packages takes time.
I'm talking hours or even days here.
</p></li>
</ul>
<h3><a name="install-first.directory">2.2 Choosing A Directory</a></h3>
<p>
Before you install, you must decide where Fink's directory hierarchy
will live. The recommended place is /sw, and all examples in this
document will use that. Any other directory should be fine as well, as
long as you don't use existing directories like /usr/local or
/usr. The bootstrap script tries to catch these.
</p>
<p>
The directory that you choose must not contain any spaces or similar characters.
Both Unix itself and the bulk of Unix software were written under this
assumption.
Using symlinks to trick the bootstrap script simply won't work.
</p>
<h3><a name="install-first.install">2.3 Installation</a></h3>
<p>
First, you need to unpack the fink-0.41.1.tar.gz tarball (it might also show up as <tt style="white-space: nowrap;">fink-0.41.1.tar</tt> if you
used Safari to download it). So, in a terminal window, go to the directory where you put the tarball, and run this
command:
</p>
<pre>tar xf fink-0.41.1.tar.gz</pre>
<p>
You now have a directory named fink-0.41.1.
Change to it with <tt style="white-space: nowrap;">cd fink-0.41.1</tt>.
</p>
<p>
The actual installation is performed by the perl script
bootstrap.
So, to start installation, go to the fink-0.41.1 directory and run
this command:
</p>
<pre>./bootstrap</pre>
<p>
After running some tests, the script will ask you what method should
be used to gain root privileges.
The most useful choice is 'sudo'.
On a default install of Mac OS X, sudo is already enabled for the user
account created during installation.
The script will immediately use the method you choose to become root.
This is required for the installation.
</p>
<p>
Next, the script will ask you for the installation path.
See 'Choosing A Directory' above for hints about this.
The script will create the directory and set it up for the bootstrap
that will be done later.
</p>
<p>
Next up is Fink configuration.
The process should be self-explaining.
You will be asked how you want to set up
fink's build user account. If you are on a networked system where
the users and groups are on a central server, you can select the
parameters manually--check with your network administrator as to
what to use.
You will also be asked about proxies--again, check with your network
administrator, and to select mirror sites for downloads.
If you don't know what to say, you can just press Return and Fink will
use a reasonable default value.
</p>
<p>
Finally, the script has enough information to conduct the bootstrap
process.
That means it will now download, build and install some essential
packages.
Don't worry if you see some packages apparently being compiled twice.
This is required because to build a binary package of the package
manager, you first must have the package manager available.
</p>
<p>Note: on 10.8, 10.9, and 10.10, after you start the install process you may see
dialog windows asking whether you want to install XQuartz.
If you want to do so, go ahead. You won't have to stop the Fink install
to do that.</p>
<p>
After the bootstrap procedure finishes, run<tt style="white-space: nowrap;">/sw/bin/pathsetup.sh</tt>
to help set up your shell environment for use with Fink. In most cases, it will run
automatically, and prompt you for permission to make changes. If
the script fails, you'll have to do things by hand (see below).</p>
<p>
(If you need to do things by hand, and you are using csh or tcsh,
you need to make sure that the command
<tt style="white-space: nowrap;">source /sw/bin/init.csh</tt> is executed during startup of
your shell, either by .login, .cshrc, .tcshrc, or something else
appropriate. If you are using bash or similar shells, the command
you need is <tt style="white-space: nowrap;">. /sw/bin/init.sh</tt>, and places where it
might get executed include .bashrc and .profile.)
</p>
<p>
Once your environment is set up, start a new terminal window to ensure that
the changes get implemented. You will now need to have Fink download package
descriptions for you.</p>
<p>
You can use
</p>
<pre>fink selfupdate-rsync</pre>
<p>
to download package descriptions using rsync. This is the preferred option for
most users, since it is quick and there are multiple mirror sites available.
</p>
<p>
However, rsync is often blocked by network administrators. If your firewall
doesn't allow you to use rsync, then you can try
</p>
<pre>fink selfupdate-cvs</pre>
<p>
to download package descriptions using cvs. If you have an HTTP proxy set up, fink
will pass its information along to cvs. Note: you can only use anonymous cvs (pserver)
through a proxy.
</p>
<p>
You can now use <tt style="white-space: nowrap;">fink</tt> commands to install packages.
</p>
<pre>fink --help</pre>
<p>
is a useful place to get more information about how to use <tt style="white-space: nowrap;">fink</tt>.
</p>
<h3><a name="install-first.x11">2.4 Getting X11 Sorted Out</a></h3>
<p>
Fink uses virtual packages to declare dependencies on X11. As of
OS 10.6, we don't provide any packages of our own. The supported options are:
</p>
<ul>
<li><p>10.9: Only XQuartz 2.7.4 and later.</p></li>
<li><p>10.10-11: Only XQuartz 2.7.7 and later.</p></li>
</ul>
<p>
For more information on installing and running X11, refer to the
online <a href="/doc/x11/">X11 on Darwin
and Mac OS X document</a>.
</p>
<h2><a name="install-up03">3 Upgrading Fink</a></h2>
<p>
You can update Fink with the built-in 'selfupdate' command. Note: this is <b>not</b>
guaranteed to be sufficient if you updated OS X.
</p>
<h3><a name="install-up03.packman">3.1 Updating The Package Manager</a></h3>
<p>
To update Fink, run the following command:
</p>
<pre>fink selfupdate</pre>
<p>
This will automatically update your existing Fink installation to
use the latest package manager, and also update all essential
packages. However, it will not update any other packages.
</p>
<h3><a name="install-up03.update-all">3.2 Updating Packages</a></h3>
<p>
The above updating steps will not update the actual packages, they
only provide you with the means to do so. The easiest way to get the
new packages is to use the 'update-all' command:
</p>
<pre>fink update-all</pre>
<p>
This will bring all installed packages to the latest version.
If you don't want to do this (it may take some time), you can update
individual packages with the 'update' command.
</p>
<h2><a name="install-up02">4 Clean Upgrade</a></h2>
<p>
There are situations, which normally don't come up every day, in which you
may find that you need to install Fink over again.
</p>
<h3><a name="install-up02.cleaninst">4.1 Situations Calling for a Clean Reinstall</a></h3>
<ul>
<li>
<p>You want to move Fink to a different path.</p>
</li>
<li>
<p>You want to update, or have already updated, OS X between versions
where Fink doesn't support an upgrade path:</p>
<p>- 10.4 -> 10.6+</p>
<p>- 10.5 -> 10.7+</p>
<p>- 10.6 -> 10.7+</p>
<p>- 10.8- -> 10.9+</p>
</li>
<li>
<p>Your Fink installation has linked to libraries, e.g. from MacPorts
or <tt style="white-space: nowrap;">/usr/local</tt>, which have been removed from
your machine thereby breaking some of your Fink libraries and
executables.</p>
</li>
</ul>
<h3><a name="install-up02.backup">4.2 Backing up to save time</a></h3>
<p>
To save time after you have reinstalled Fink, you can get a transcript
of your installed packages. The following command in a terminal window
will work, even if for some reason the Fink tools aren't functioning:
</p>
<pre>grep -B1 "install ok installed" /sw/var/lib/dpkg/status \
| grep "^Package:" | cut -d: -f2 | cut -d\ -f2 > finkinst.txt</pre>
<p>
This will save the list of your packages in the file <tt style="white-space: nowrap;">finkinst.txt</tt>
in the current working directory.
</p>
<p>
You may also want to copy or move the sources in <tt style="white-space: nowrap;">/sw/src</tt>
to another location so that you don't have to spend time downloading them when
you begin restoring your Fink distribution.
</p>
<p>
In addition, if you have made global configuration changes to any of your packages by
editing configuration files in <tt style="white-space: nowrap;">/sw/etc</tt>, then you may wish to back
those up.
</p>
<h3><a name="install-up02.removing">4.3 Removing Your Old Fink</a></h3>
<p>
Once you've <a href="#install-up02.backup">backed everything up</a>, you are ready
to remove your Fink distribution. You can remove <tt style="white-space: nowrap;">/sw</tt> as well as
anything in <tt style="white-space: nowrap;">/Applications/Fink</tt>
using the Finder or the command line:
</p>
<pre>sudo rm -rf /sw /Applications/Fink/*</pre>
<p>
(Replace <tt style="white-space: nowrap;">/sw</tt> by your actual Fink tree).
</p>
<h3><a name="install-up02.reinstalling">4.4 Installing Fink Again</a></h3>
<p>
First, follow the <a href="#install-first">first-time install instructions</a>.
</p>
<p>
Once you have downloaded package descriptions, you can put the sources that you
<a href="#install-up02.backup">backed up</a> into <tt style="white-space: nowrap;">/sw/src</tt> either
using the Finder or the command line:
</p>
<pre>sudo cp /path/to/backup/* /sw/src</pre>
<p>
(As usual, replace <tt style="white-space: nowrap;">/sw</tt> with your Fink tree). If you prefer, you can
use <tt style="white-space: nowrap;">fink configure</tt> to specify your backup location:
</p>
<pre>In what additional directory should Fink look for downloaded tarballs? []
<b>(enter your backup directory at the prompt)</b>.
</pre>
<p>
Note: this requires that the entire path to and including your backup directory is world-readable.
</p>
<p>
You can also restore your global configuration files at this time.
Note: we recommend that you <b>not</b> restore <tt style="white-space: nowrap;">/sw/etc/fink.conf</tt>
from your prior installation of Fink, to avoid incompatibilities. You can open it up
in a text editor and enter the correponding values into <tt style="white-space: nowrap;">fink configure</tt>.
</p>
<hr><h2>Copyright Notice</h2><p>Copyright (c) 2001 Christoph Pfisterer,
Copyright (c) 2001-2016 The Fink Project.
You may distribute this document in print for private purposes,
provided the document and this copyright notice remain complete and
unmodified. Any commercial reproduction and any online publication
requires the explicit consent of the author.</p><hr>
<p>Generated from <i>$Fink: install.xml,v 1.49 2015/10/04 00:00:05 alexkhansen Exp $</i></p></body></html>