--nextPart2523255.9mldFAk4Pt
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Stephan Kulow wrote:
>Hmm, this means everyone has to check out KDE/3.5 exactly this way, no?

At least kde-common inside it.

>I don't like this at all. I want to have full control where to place my
> kdelibs, I don't want to be forced to put it in $mypath/KDE/3.5/kdelibs

That's a downside of using relative paths.

>And this does not only apply to branches but also in trunk you would
> need to have a KDE subdir checked out - if you want or not. The
> symlinks have to fit. Call me stubborn, but this is the killing
> argument against either symlinks or nested structures. What were the
> disadvantages of external properties again? One was that they are
> absolute so they had to be redone in branches, but if I look at your
> example this would also be an argument for KDE/ as every other app or
> module would need to redo them anyway.

True.

But I don't understand what you're proposing. Where would kde-common be?

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

1. On frumscafte, hwonne time_t w=C3=A6s n=C3=A1ht, se scieppend =C3=BEone =
circolwyrde=20
wundorcr=C3=A6ftl=C3=ADge cennede and seo eor=C3=B0e w=C3=A6s idel and hit =
w=C3=A6s g=C3=B3d.

--nextPart2523255.9mldFAk4Pt
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCTSb+M/XwBW70U1gRAlWQAJ9rE4r9qpgC2E7/FMD6bgE82cGtrwCfcNj0
7Gx2NQkwcKdncEeAEnm475M=
=C21l
-----END PGP SIGNATURE-----

--nextPart2523255.9mldFAk4Pt--