SVN: What happens to homeless modules?

[Thiago Macieira]

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?

-- 
  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æs náht, se scieppend þone circolwyrde 
wundorcræftlíge cennede and seo eorðe wæs idel and hit wæs gód.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050401/df6bbe9f/attachment.sig>