Configuration Management

[Keith P. Boruff]

On Friday 11 February 2005 11:43 am, Waldo Bastian wrote:
> On Friday 11 February 2005 10:46, Keith P. Boruff wrote:
> > Hi all,
> >
> > I spent the last few hours tracing through the scripts/makefiles/etc of
> > kdepim. The GNU autotools is a topic I wish to know more about both for a
> > project at work and because I'm just curious.
> >
> > My question is, is there a seperate group of people, project, etc who
> > handles this stuff across all KDE packages or is each group responsible
> > for maintaining their own stuff? That is, does the kdepim group maintain
> > their own configuration management stuff? From what I've seen of the
> > other packages, I'm guessing the former.
>
> A lot of KDE specific configuration management is provided as part of
> kde-common/admin which is exclusively maintained by the following people:
> matz,lunakl,coolo,faure,mueller,hausmann,staikos,waba,adridg,ossi,binner
>
> See kde-common/accounts to map the above CVS account names to real names &
> e-mail addresses.
>
> Individual CVS modules or individual applications can have their own
> specific tests on top of the functionality provided by kde-common/admin cq.
> by using tests provided by kde-common/admin
>
> See the various configure.in.in files throughout KDE.
>
> These application specific files are typically maintained by the above
> people in combination with the application maintainer(s).
>
> Typically, if new tests are needed they get added at the application level,
> if they are relevant to more applications in the same module they are being
> moved up to the module level and if they are needed in multiple modules it
> tends to be moved to kde-common.
>
> Cheers,
> Waldo

Thanks. If I asked this question in the wrong mailing list, I apologize. I 
hadn't realized until earlier today that there was one specifically for 
developers. If (rather when) this type of question arises again, I'll ask 
there. 

Again thanks, 
Keith