| 1 |
On Tue, 2006-01-10 at 19:59 +0100, Christian Parpart wrote: |
| 2 |
> On Sunday 08 January 2006 13:04, Patrick Lauer wrote: |
| 3 |
> [...] |
| 4 |
> > --> write a sane rsync_exclude (or better, start a cygwin-only ebuild |
| 5 |
> > repo) |
| 6 |
> [...] |
| 7 |
> |
| 8 |
> can't believe this to be the *better* solution. |
| 9 |
> What else do we have KEYWORDS for when not for architechtures? |
| 10 |
That's absolutely not the problem from my point of view :-) |
| 11 |
|
| 12 |
> Although, I'd rather like to see cygwin fixed, in a way it can handle such |
| 13 |
> "valid" filenames. |
| 14 |
The problem here is that Cygwin is incapable of parsing all filenames that |
| 15 |
are valid in Linux. RSYNC_EXCLUDE is the "easy" way out. Restricting filenames |
| 16 |
would work too. |
| 17 |
|
| 18 |
The only ebuild I can remember that had this problem was a CFEngine |
| 19 |
module |
| 20 |
- maybe this is no longer a problem? |
| 21 |
|
| 22 |
For patched ebuilds I'd prefer a cygwin-only repo until basic stuff |
| 23 |
works, |
| 24 |
no need to stuff another broken arch into the tree. Especially the |
| 25 |
insane |
| 26 |
gcc patches and the "new" libc should be kept away from the rest. |
| 27 |
|
| 28 |
wkr, |
| 29 |
Patrick |
| 30 |
-- |
| 31 |
Stand still, and let the rest of the universe move |
Archives