Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Jul 2005 07:59:05 -0700
From:      "Michael C. Shultz" <ringworm01@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Obtaining portsmanager meta package for alternate OS
Message-ID:  <200507150759.05814.ringworm01@gmail.com>
In-Reply-To: <200507150954.56656.ean@hedron.org>
References:  <42D6B0EA.3000501@u.washington.edu> <200507141303.43540.ringworm01@gmail.com> <200507150954.56656.ean@hedron.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 15 July 2005 06:54, Ean Kingston wrote:
> On July 14, 2005 04:03 pm, Michael C. Shultz wrote:
> > On Thursday 14 July 2005 11:37, Garrett Cooper wrote:
> > > Hello,
> > >     I was wondering if anyone could point me to the release notes or
> > > code so I could look up the dependencies for the portsmanager package
> > > and possibly compile it on Mac OS X Tiger.
> >
> > Try running configure then make just like any other linux program and see
> > if it compiles, if it doesn't let me know what the error is.  I
> > understand Mac OS X is based on FreeBSD, does it have FreeBSD's port
> > infrastructure?
>
> My Mac (OSX 10.2) doesn't have anything remotely resembling a port
> infrastructure installed as part of the OS. All the OSS that I've installed
> was done through what I will call binary 'bundles' mostly from .dmg files.
> They each provided their own installer (usually using the applescript
> langauge).


Too bad for Apple, the ports system is what makes FreeBSD shine, no point
in trying to get portmanager running in OS X in any case.

-Mike



>
> For those who might care, a .dmg file is a mac disk image and seams to be
> the mac equivolent of tar.
>
> Sometimes the installer is a text file that says move the files to your
> applications directory.
>
> > For example can you do things like:
> > make
> > make install
> > make package
> > make deinstall
> > ???
>
> You would need to install a compiler.
>
> > If the above work diferently or /var/db/pkg/* is different then
> > portmanager won't work.  Would be interesting to know the
> > similarities/differences between FreeBSD and Mac OS X ports
> > infrastructure.
>
> /var isn't really used by the MAC except for /var/log and /var/run.
>
> > As far as portmanager's dependices, to run it requires libc and to
> > compile just needs standard autotools if I recall correctly.
> >
> > >     My FreeBSD machine is currently at home (sadly without an internet
> > > connection to the outside world :(), and I would like to keep it up to
> > > date by periodically fetching the ports 'source files'/packages and
> > > port snapshots. So I thought I could accomplish this via building the
> > > portsmanager package and running it off of my laptop at school since
> > > it's the only way I can accomplish my task at hand.
> > >     However, with that in mind, I was wondering if there was a better
> > > way to fetch ports/packages without having to manhandle too many
> > > programs/scripts, or if anyone has discovered a better solution to this
> > > type of 'issue'.
> > >     Thanks and your responses are greatly appreciated as solving this
> > > 'problem' will help save me a great deal of time :)!
> > > -Garrett
> >
> > To use portmanager this way you'll need a way to keep your ports tree
> > current and a way to get the current distfiles. If you can do these two
> > things somehow then just drop the current distfiles into
> > /usr/ports/distfiles and update your ports tree and portmanager should
> > run OK.
> >
> > -Mike



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507150759.05814.ringworm01>