> Who knows, maybe I'll pickup this project this Winter if I have time for
> a day or two.  Usually I tend to spend time programming C though.
>
> Looking at the Gentoo Cygwin wiki, does look like the majority of the
> work is completed. :-)

*sigh*  If only that were so...

I'm the one who wrote the bulk of the wiki article.

I cranked out a patch for Portage right before there was a major
version change (I use "major version" in a spiritual sense), and there
have been several major revisions since then.  The trickiest part of
the whole mess is that Cygwin remaps paths prefixed with // to UNC
paths, resulting in long pauses followed by failures (while portage
expects // to be the same as /).  I tried to be "good" about it in my
work and let portage use // when it *really* wants to (conceivably to
install to paths over Samba), but in hindsight, that was probably far
too optimistic a goal and pointless a purpose.  There were also some
hard-coded blocks against uname's output that had to be
circumvented...

I've hypothesized, to myself, that prefixed portage may work for
Cygwin, but I haven't looked very carefully.

The Cygwin community has been very closed to the idea of admitting
Portage (I've tried), even in light of other package management
systems (like RPM) that they support.  As an alternative, they have a
Portage-like build system (for building setup.ini packages) called
cygport, whose community of packages I've seen mentioned elsewhere in
this thread.

The Cygwin chapter of my life has spanned from 1998 to the present,
but it's drawing to a close.  Before long, I expect to leave the
Windows world entirely.  Best of luck to you, though I'll keep an eye
on this mailing list and offer what advice I can.

Regards,
Jason

>
> --
> Roger
> http://www.eskimo.com/~roger/index.html
> Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61
>
> Thu Dec 20 14:01:09 AKST 2007
>
>
> --
> gentoo-cygwin@g.o mailing list
>
>
-- 
gentoo-cygwin@g.o mailing list