1 |
Patrick Lauer wrote: |
2 |
|
3 |
>Well - |
4 |
> |
5 |
>first you'd need to fix portage for Cygwin usage. Small stuff: |
6 |
>- user/group check is not reliable in windows |
7 |
> * either remove or add "root" and "portage" users |
8 |
>- there's some userland check that fails, need to append WINNT5.0 if I |
9 |
>recall correctly |
10 |
>- there were some path issues, I think those are fixed - hardcoded paths |
11 |
>need to be fixed |
12 |
> |
13 |
>So portage mostly runs. |
14 |
>emerge sync doesn't work as we have a few ebuilds with ":" in the name |
15 |
>--> cygwin interprets that as a drive letter |
16 |
>--> write a sane rsync_exclude (or better, start a cygwin-only ebuild |
17 |
>repo) |
18 |
> |
19 |
>Now you try bootstrapping. |
20 |
>--> the linker used to be really dumb and wasn't capable of repeated |
21 |
>compiles. |
22 |
> * if that still exists the linker needs to be fixed - this will be |
23 |
>tricky |
24 |
>--> glibc doesn't exist on Cygwin, the cygwin libc is evil |
25 |
> * either write an ebuild for cygwin-libc providing virtual/libc or port |
26 |
>glibc |
27 |
> * I never managed to build cygwin-libc from scratch, it's evil :-) |
28 |
> * porting glibc will be _a lot_ of work, cygwin libc is incomplete |
29 |
>--> many packages need lots of patching |
30 |
> * extract patches from cygwin repositories, apply to ebuilds and test |
31 |
> * never managed to get gcc to build, that'll be lots of testing until |
32 |
>it works reliably |
33 |
>--> now you should have a smallish system that can "emerge -e system" |
34 |
> |
35 |
>--> create an install image like the cygwin installer that plops in a |
36 |
>stage3 equivalent |
37 |
> |
38 |
>--> start porting as many ebuilds as you can |
39 |
> |
40 |
>People with some spare time and lots of motivation can try "Services for |
41 |
>Unix" instead of Cygwin |
42 |
>as far as I can tell it's not as buggy, but has been crippled so that |
43 |
>it's not easy to use. |
44 |
> |
45 |
>Cygwin and SFU can co-exist and should share 99% of code, so trying both |
46 |
>is acceptable |
47 |
> |
48 |
>I don't have the time for actual coding/testing now, but I'm willing to |
49 |
>provide ressources (rsync repo, cvs / svn repo, coordination) |
50 |
> |
51 |
>If there are any questions left feel free to ask! |
52 |
> |
53 |
>wkr, |
54 |
>Patrick |
55 |
> |
56 |
> |
57 |
> |
58 |
These are "nice to know" points. If you remember anything else, pls let |
59 |
me know. Tks |
60 |
|
61 |
I have started to working on it (for fun) in my spare time and I am |
62 |
having some success. I have set up the user/group in Cygwin to look more |
63 |
like Linux which is mostly working. I added the os definitions which |
64 |
were missing from portage. I am now at the stage where the file locks |
65 |
are not getting removed. |
66 |
|
67 |
The ":" might be tricky, however, I could use a managed mount for |
68 |
portage. Perhaps the offending packages could simply be renamed. |
69 |
|
70 |
I am only interested in getting Cygwin working so SFU not in my scope. I |
71 |
have not found Cygwin buggy, and even if it were broken, its just code |
72 |
that can be fixed... Do you have examples... |
73 |
|
74 |
|
75 |
Tks |
76 |
Trevor |
77 |
|
78 |
|
79 |
|
80 |
|
81 |
|
82 |
|
83 |
-- |
84 |
gentoo-cygwin@g.o mailing list |