KDE 4 modules structure (again)

[Olivier Goffart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Dimanche 14 Mars 2004 18:11, Dominique Devriese a écrit :
> Thiago Macieira writes:

> > Isn't there a way of making it a recursive structure? For instance,
> > checking out "kdebase" gets you all the apps and one configure for
> > all of them, but checking out "kdebase/kicker" gets you kicker
> > alone, with its own configure, which you could place side by site to
> > "kdebase/kdm" in order to make packages and/or release tarballs.
>
> I like this idea.  It has the potential to combine the advantages of
> both approaches.  I think the technical problems with it ( configure
> checks that are needed by more than one app in e.g. kdebase ) can be
> fixed by moving them into a autoconf macro, and then making judicious
> use of AC_REQUIRE.

cvs co -l kdebase
cvs co kdebase/kicker
ln -s kde-common/admin kdebase/admin

it's not realy difficult.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAVJV4z58lY8jWrL0RAu7CAJ9bMCTB2W3W5SLeaVjnJ1zsEv/kmQCeKQut
4bLaE3FNABO9rl+4/r/jCGI=
=cCuL
-----END PGP SIGNATURE-----