[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: admin dir [was No Makefile.am in kdeartwork cvs KDE_3_1_0_RELEASE]
From:       Alan Chandler <alan () chandlerfamily ! org ! uk>
Date:       2002-11-27 20:16:20
[Download RAW message or body]

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

On Wednesday 20 November 2002 8:24 pm, Ross Boylan wrote:
> On Wed, Nov 20, 2002 at 05:57:10PM +0100, Dirk Mueller wrote:
> > On Die, 19 Nov 2002, James Richard Tyrer wrote:
> > > Specifically:
> > >
> > > 	ln -s ../kde-common/admin
> > >
> > > You might need to delete an existing: "admin/" directory first.
> >
> > Nope. don't do that when you use *cvs*. *Only* do this when using
> > *cvsup*.
>
> Oh my.  Could you explain that?  I'm using cvsup, and wasn't aware it
> made any difference once I got the sources where they came from.
>
> Ahh.. is it that kdefoo is aliased to kdefoo and admin in cvs, but
> only gets kdefoo in cvsup?  Even so, why should I need to delete an
> existing admin directory?
>

I have been trying to build the debian packages from anoncvs and some of the 
modules (kdepim was one) run a script inside admin called cvs-clean.pl

I downloaded a tagged release from anon cvs and it didn't include the admin 
directory  (I don't know why - I could only assume that it is because the cvs 
"module" file doesn't have any of the release tags on it) - so I linked it in 
as described above..

This script (called by the debian rules script) deleted the directory again 
because it wasn't inside the CVS directory.

The trick is to cd kdefoo and then do "cvs co admin".

- -- 
Alan Chandler
alan@chandlerfamily.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE95SgUuFHxcV2FFoIRApzeAJkBhp197m7L+v4CBNcSoGbuxvQhhQCdHD9w
RZiRs0v9Hca17fMHoKPi8Qg=
=ouXg
-----END PGP SIGNATURE-----

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]