public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph Hardin <jhlazer@charter.net>
To: Nicholas Wourms <dragon@gentoo.org>
Cc: Daniel Robbins <drobbins@gentoo.org>,
	Taylor Christopher P <ct@cs.clemson.edu>,
	Pieter Van den Abeele <pvdabeel@gentoo.org>,
	gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage Ported to OS X
Date: Tue, 3 Jun 2003 19:16:03 -0600	[thread overview]
Message-ID: <1BE67C40-962A-11D7-B88A-000A95686F0A@charter.net> (raw)
In-Reply-To: <3EDD2B5D.2000606@gentoo.org>

I have a Powerbook G4 Ti(1ghz) that i'd be willing to help test stuff 
with.
								Joe

On Tuesday, Jun 3, 2003, at 17:12 America/Denver, Nicholas Wourms wrote:

> Daniel Robbins wrote:
>> On Tue, Jun 03, 2003 at 05:42:34PM -0400, Taylor Christopher P wrote:
>>> when you say "open bug" whatcha mean? oh, and i need people to help 
>>> me
>>> figure out somethings with the source... i remember vlad from my 
>>> early
>>> gentoo-ppc days. i'll need to email them both...
>>>
>>> thanks!
>> Probably best if I get Portage working initially under OS X. I've 
>> started
>> the port today and I'm not expecting that much difficulty -- should 
>> have it
>> mostly done some time today. We can officially support OS X and make 
>> this
>> into an official Gentoo project hosted on www.gentoo.org. :)
>> Best Regards,
>
> I've have a MacOS X machine as well, so I'd be willing to help test 
> and perhaps contribute (as time allows)...  IIRC, SpanKY has an OS X 
> machine as well, so I'd say we are pretty much covered in the OS X 
> department :-D.
>
> One thing to note, libtool support on OS X sucks bug time, especially 
> with libtool-1.4.  We should give some thought to integrating a 
> libtool 1.5 ebuild now that it is released and stable.
>
> Cheers,
> Nicholas
>
>
> --
> gentoo-dev@gentoo.org mailing list
>


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-04  5:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03  1:02 [gentoo-dev] Portage Ported to OS X Taylor Christopher P
2003-06-03  2:25 ` Daniel Robbins
2003-06-03 21:35   ` Pieter Van den Abeele
2003-06-03 21:42     ` Taylor Christopher P
2003-06-03 21:54       ` Pieter Van den Abeele
2003-06-03 22:07       ` Daniel Robbins
2003-06-03 22:34         ` Jon Portnoy
2003-06-03 22:38           ` Pieter Van den Abeele
2003-06-07 23:20             ` Alvaro Figueroa
2003-06-09 22:59               ` Luke-Jr
2003-06-10  2:08                 ` Taylor Christopher P
2003-06-04  0:56           ` Taylor Christopher P
2003-06-03 23:12         ` Nicholas Wourms
2003-06-04  1:16           ` Joseph Hardin [this message]
2003-06-04 15:07             ` Sascha Schwabbauer
2003-06-04 16:39               ` oford
2003-06-04 20:06                 ` Joseph Hardin
2003-06-04  8:52         ` Joseph Carter
2003-06-10  0:01           ` leon j. breedt
2003-06-10 12:47             ` Joseph Carter
     [not found]         ` <20030604082858.GE10084@galen>
2003-06-04 13:05           ` Taylor Christopher P
     [not found] <Pine.GSO.4.51.0306040902350.736@yoda.cs.clemson.edu>
2003-06-04 13:41 ` Pieter Van den Abeele

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=1BE67C40-962A-11D7-B88A-000A95686F0A@charter.net \
    --to=jhlazer@charter.net \
    --cc=ct@cs.clemson.edu \
    --cc=dragon@gentoo.org \
    --cc=drobbins@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=pvdabeel@gentoo.org \
    /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