1 |
On Sun, 2006-01-08 at 12:23 +0100, Marcus Priesch wrote: |
2 |
> On Sun, 2006-01-08 at 09:59 +0100, Patrick Lauer wrote: |
3 |
> > Interest yes, manpower no as far as I can tell. |
4 |
> > |
5 |
> > I'd really like to see it go somewhere ... |
6 |
> |
7 |
> is there a point to where someone can find information on work that |
8 |
> needs to be done ? - what are the main points ? |
9 |
Well - |
10 |
|
11 |
first you'd need to fix portage for Cygwin usage. Small stuff: |
12 |
- user/group check is not reliable in windows |
13 |
* either remove or add "root" and "portage" users |
14 |
- there's some userland check that fails, need to append WINNT5.0 if I |
15 |
recall correctly |
16 |
- there were some path issues, I think those are fixed - hardcoded paths |
17 |
need to be fixed |
18 |
|
19 |
So portage mostly runs. |
20 |
emerge sync doesn't work as we have a few ebuilds with ":" in the name |
21 |
--> cygwin interprets that as a drive letter |
22 |
--> write a sane rsync_exclude (or better, start a cygwin-only ebuild |
23 |
repo) |
24 |
|
25 |
Now you try bootstrapping. |
26 |
--> the linker used to be really dumb and wasn't capable of repeated |
27 |
compiles. |
28 |
* if that still exists the linker needs to be fixed - this will be |
29 |
tricky |
30 |
--> glibc doesn't exist on Cygwin, the cygwin libc is evil |
31 |
* either write an ebuild for cygwin-libc providing virtual/libc or port |
32 |
glibc |
33 |
* I never managed to build cygwin-libc from scratch, it's evil :-) |
34 |
* porting glibc will be _a lot_ of work, cygwin libc is incomplete |
35 |
--> many packages need lots of patching |
36 |
* extract patches from cygwin repositories, apply to ebuilds and test |
37 |
* never managed to get gcc to build, that'll be lots of testing until |
38 |
it works reliably |
39 |
--> now you should have a smallish system that can "emerge -e system" |
40 |
|
41 |
--> create an install image like the cygwin installer that plops in a |
42 |
stage3 equivalent |
43 |
|
44 |
--> start porting as many ebuilds as you can |
45 |
|
46 |
People with some spare time and lots of motivation can try "Services for |
47 |
Unix" instead of Cygwin |
48 |
as far as I can tell it's not as buggy, but has been crippled so that |
49 |
it's not easy to use. |
50 |
|
51 |
Cygwin and SFU can co-exist and should share 99% of code, so trying both |
52 |
is acceptable |
53 |
|
54 |
I don't have the time for actual coding/testing now, but I'm willing to |
55 |
provide ressources (rsync repo, cvs / svn repo, coordination) |
56 |
|
57 |
If there are any questions left feel free to ask! |
58 |
|
59 |
wkr, |
60 |
Patrick |
61 |
|
62 |
> greets, |
63 |
> mexx (a somesparetimeavailablenowgentooenthusiast). |
64 |
> |
65 |
-- |
66 |
|
67 |
-- |
68 |
gentoo-cygwin@g.o mailing list |