From: Skeezics Boondoggle <skeezics@q7.com>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: SDL Interface Development
Date: Sun, 31 Oct 2004 19:50:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0410311108330.5719-100000@q7.q7.com> (raw)
In-Reply-To: <1099249482.26829.6236.camel@localhost>
On Sun, 31 Oct 2004, Lincoln Peters wrote:
> You should be able to run apt-get on Solaris, and use that to resolve
> the dependencies. I found a post on the Debian archives that indicates
> that apt-get will compile and run on Solaris, but I don't have Solaris
> so I can't vouch for it:
Well, for Solaris 2.6 and 7 I built extensive libraries of RPMs for
Solaris; I'm planning a complete Solaris 8 environment at home (since I
have a lot of older sun4d hardware that's EOL'ed after Sol8), and I've
played with 9 a bit at work, and now with 10 coming... I'm not sure if I
have the physical stamina needed to build full-blown RPM support for all
those platforms. 25 years of banging on keyboards is finally taking its
toll, and my hands ache just thinking about it.
I've used apt-get (with "Fink") on my son's Mac OS X box, and it seems
fine. But I'm not sure I want to bother with another packaging scheme for
Solaris. So,
Solaris native packages are slow and horrible;
RedHat started making RPM far too Linux-specific and annoying;
OpenPKG seemed like a good direction, but they made a bunch of
stupid/annoying decisions too;
The old "make install" route went out of vogue with SunOS4;
I really don't need to learn Yet Another Packaging System now,
because I'm too old/lazy/tired.
So, basically, I'm screwed. :-) Unless I want to rely on one of the Sun
freeware sites, and they never quite do things the way I like. Sigh.
For now, I'll just stick with RPM. When I get a free moment I'll try a
Solaris 7 build, and report back on how that goes.
-- Chris
next prev parent reply other threads:[~2004-10-31 19:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 23:28 Eric McDonald
2004-10-31 4:10 ` Lincoln Peters
2004-10-31 6:13 ` Eric McDonald
2004-10-31 6:34 ` Elijah Meeks
2004-10-31 7:34 ` Lincoln Peters
2004-10-31 18:39 ` Eric McDonald
2004-10-31 18:23 ` Eric McDonald
2004-10-31 6:54 ` D. Cooper Stevenson
2004-10-31 18:26 ` Eric McDonald
2004-10-31 16:28 ` Skeezics Boondoggle
2004-10-31 19:04 ` Lincoln Peters
2004-10-31 19:50 ` Skeezics Boondoggle [this message]
2004-10-31 19:04 ` Eric McDonald
2004-11-07 8:29 ` Publicity Test Run Elijah Meeks
2004-11-13 23:23 ` New Source Tarball and Windows Installer (was Re: Publicity Test Run) Eric McDonald
2004-11-13 23:55 ` Publicity Test Run Lincoln Peters
2004-11-14 0:54 ` Eric McDonald
2004-11-14 22:31 ` Lincoln Peters
2004-10-31 17:45 Re: SDL Interface Development ejessen
2004-10-31 18:08 ` D. Cooper Stevenson
2004-10-31 18:57 ` Lincoln Peters
2004-10-31 19:09 ` Eric McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0410311108330.5719-100000@q7.q7.com \
--to=skeezics@q7.com \
--cc=sampln@sbcglobal.net \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).