gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnumed-devel] (Debian) apt-get + Synaptic = (Mac OS 3rd party) MacPorts


From: Jim Busser
Subject: [Gnumed-devel] (Debian) apt-get + Synaptic = (Mac OS 3rd party) MacPorts + Porticus?
Date: Mon, 31 Aug 2009 20:03:02 -0700

On my Mac, I have downloaded and installed MacPorts and also Porticus, and am now further examining them. Looking at the nice documentation at

http://guide.macports.org/  (particularly 6.2 Configuration Files)

these make me think of Debian's apt-get and Synaptic. On quick parsing:

1) looks like MacPorts can script the alteration required to the psycopg2 setup.cfg file
2) looks like MacPorts can generate packages and disk images
3) if myself or anyone does get a portfile set up, it might be interesting to test whether a generated rpm works as advertised :-)

==================
3.4. Port Binaries

MacPorts can pre-compile ports into binaries so applications need not be compiled when installing on a target system. MacPorts may create two types of binaries: archives and packages.

3.4.1. Binary Archives

Binary archives can only be used on a target system running MacPorts. Binary archives allow MacPorts utilities to begin installation after the destroot phase and install and activate a port on the target system.


3.4.2. Binary Packages

Binary packages are standalone binary installers that are precompiled; they do not require MacPorts on the target system. Binary files created with MacPorts may be either .pkg (Mac OS X Installer Packages), or RPM (RPM Package Manager) format. MacPorts may also process a .pkg package into a Mac OS X .dmg disk image file.

You may create binary packages with the portcommand as shown in these examples.

	%% port pkg pstree

You may create a Mac OS X .dmg disk image file as shown:

	%% port dmg pstree

You may compile a port into an RPM file as shown, in order to install it onto a target that has RPM utilities or a full package management system that can install RPMs:

	%% port rpm pstree
==================
5.6. Tcl Extensions

A MacPorts Portfile is a Tcl script, so it may contain any arbitrary Tcl code you may learn about in a Tcl reference manual. However, few authors will use arbitrary Tcl code; the vast majority will use Tcl extensions that are coded within MacPorts for performing the most common tasks needed for Portfiles. The list below is a list of Tcl extensions provided by MacPorts base.

file (copy, move, rename, delete [-force], mkdir)

macros (copy, move, delete file ..., touch, ln)

xinstall

reinplace … Allows text specified by a regular _expression_ to be replaced by new text, in-place (the file will be updated itself, no need to place output into a new file and rename).

reinplace [-E] [--] command file ... Replace text given by the regular _expression_ portion of the command with the replacement text, in all files specified.

==================
6.2. Configuration Files

There are three MacPorts configuration files that define important variables used by the MacPorts system: macports.conf, sources.conf, and variants.conf. All MacPorts configurations files are located in ${prefix}/etc/macports.

MacPorts configuration file format is a simple key/value pair separated by either a space or a tab. Lines beginning with '#' are comments, empty lines are ignored.

==================
6.2.1. macports.conf

applications_dir

Directory to install MacPorts that install Mac OS X .app bundles.

Default: /Applications/MacPorts

frameworks_dir

Directory to install frameworks installed by ports.

Default: ${prefix}/Library/Frameworks

==================


reply via email to

[Prev in Thread] Current Thread [Next in Thread]