1 |
roger wrote: |
2 |
> On Wed, 2007-12-19 at 14:30 -0800, Eddie Parker wrote: |
3 |
> |
4 |
> |
5 |
>> Anyhow, is there anyone listening/reading this mailing list anymore? |
6 |
>> What's the status of this project, if so? |
7 |
>> |
8 |
> |
9 |
> I'm listening, but there hasn't been much activity as far as I know. |
10 |
> |
11 |
> I think most would rather spend time programming a native linux program. |
12 |
> |
13 |
> 4 or 5 years ago, I used to spend time debugging programs for porting to |
14 |
> cygwin or windows, but I have advanced to other things now. |
15 |
> |
16 |
> |
17 |
I can't say I blame you. I've been following the instructions on the |
18 |
wiki [1], and while I've got it working, it seems that most packages |
19 |
require tweaking to get to work... I can imagine the debugging would be |
20 |
intensive to, when things don't work. :( |
21 |
|
22 |
That said, if there are people who are interested in this sort of stuff, |
23 |
it might be nice to see what the status of the previous project |
24 |
was(/is?). Top of my mind are questions such as: |
25 |
|
26 |
1.- Does anyone know if the Gentoo community is/was willing to have the |
27 |
'Cygwin' arch as a 'supported' arch within portage? [2] |
28 |
2.- Did any of the previous maintainers/visionaries for this project |
29 |
have any thoughts about replacing in-use files such as Python? Be-it |
30 |
through windows' typical "reboot" methodology or some such? |
31 |
3.- At the very least, was it/would it be possible to have a script that |
32 |
create a portage overlay from Cygwin's setup.ini, so you can get binary |
33 |
packages installed with emerge as a start? |
34 |
|
35 |
I'm not naive enough to think I'm the only one to've thought of these |
36 |
things, so I'm actually just curious if there were technical limitations |
37 |
to any/all of these that I'm not aware of. Just trying to get a read of |
38 |
how this project went! |
39 |
|
40 |
Cheers, |
41 |
|
42 |
-e- |
43 |
|
44 |
[1] http://gentoo-wiki.com/HOWTO_Gentoo_on_Cygwin |
45 |
[2] I'm not sure if I'm using the right terminology, basically to have |
46 |
it be an ACCEPTED_KEYWORD, and having ebuilds as part of portage that |
47 |
support it? |