[MiNT] Adding MiNT support to pkgsrc?

[David Brownlee <abs@absd.org>]

Anyone interested in adding MiNT support to pkgsrc?

pkgsrc is a source/binary based packaging system which has been
ported to a quite a few operating systems (from
http://www.netbsd.org/docs/software/packages.html#platforms -
NetBSD, Solaris, Linux, Darwin (Mac OS X), FreeBSD, OpenBSD, IRIX,
BSD/OS, AIX, Interix (Microsoft Windows Services for Unix),
DragonFlyBSD, OSF/1, HP-UX, QNX )

In quite a few cases it acts as a repository for patches to enable
support for operating systems or architectures when upstream
developers are not interested in integrating them. Since NetBSD
runs on a variety of m68k platforms quite a few packages will have
had general m68k support added to them - for example a recent build
list of NetBSD/atari m68k packages is at
ftp://ftp.netbsd.org/pub/NetBSD/packages/4.0/atari/All/

Since there are many people working on it and updating packages to
the latest versions you tend to find that a package with patches for
a more obscure platform will get rolled forward when a package is
updated.

Assuming a functional gcc on the system then someone would start
at http://www.netbsd.org/docs/pkgsrc/porting.html and then try
installing the pkgrsc bootstrap
http://www.netbsd.org/docs/pkgsrc/platforms.html#bootstrapping-pkgsrc

> From the 'Why pkgsrc' section of the general pkgsrc docs -
http://www.netbsd.org/docs/software/packages.html

    * Easy building of software from source as well as the creation
      and installation of binary packages. The source and latest
      patches are retrieved from a master or mirror download site,
      checksum verified, then built on your system. Support for
      binary-only distributions is available for both native platforms
      and NetBSD emulated platforms.
    * All packages are installed in a consistent directory tree,
      including binaries, libraries, man pages and other documentation.
    * Package dependencies, including when performing package
      updates, are handled automatically. The configuration files of
      various packages are handled automatically during updates, so
      local changes are preserved.
    * Like NetBSD, pkgsrc is designed with portability in mind and
      consists of highly portable code. This allows the greatest
      speed of development when porting to new a platform. This
      portability also ensures that pkgsrc is consistent across all
      platforms.
    * The installation prefix, acceptable software licenses,
      international encryption requirements and build-time options
      for a large number of packages are all set in a simple, central
      configuration file.
    * The entire source (not including the distribution files) is
      freely available under a BSD license, so you may extend and
      adapt pkgsrc to your needs. Support for local packages and
      patches is available right out of the box, so you can configure
      it specifically for your environment.