On Wed, 18 Apr 2018 16:14:58 +0200 Rainer Müller <[email protected]> wrote: > > Maybe I should ask this a bit differently. Are there other > > precedents for using a "foreign" packaging or build system and > > tricking it into building stuff for macports that I could study > > and possibly steal pieces of? > > Not that I am aware of. Most package managers would also install > all the dependencies, something we do not want in a port. > > The usual approach is to generate a Portfile from the definition of > the "foreign" package manager and also create ports for all > dependencies. > > For example, cpan2port or pypi2port in macports-contrib [1,2] do > that for Perl or Python, respectively. They are far from perfect, > but are a great help to get an initial Portfile.
Maybe this is the right approach. Is this generally how ruby, python, and perl ports handle this? Perry -- Perry E. Metzger [email protected]
