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

List:       kde-devel
Subject:    Re: kpanel
From:       Peter Silva <peter.silva () videotron ! ca>
Date:       1998-11-12 14:31:05
[Download RAW message or body]

Stephan Kulow wrote:
> 
> Pietro Iglio wrote:
> >
> > At 19.04 10/11/98 +0100, Stephan Kulow wrote:
> > >Pietro Iglio wrote:
> > >>
> > >> At 09.24 10/11/98 +0100, Stephan Kulow wrote:
> > >> >Hi!
> > >> >
> > >> >Today I tried to copy my kde dir around and had to find out
> > >> >that someone put a symlink to / in it. I think, this is a
> > >> >very, very bad idea.
> > >> >
> > >> >Can't kdisknav simulate those symlinks instead of really
> > >> >setting them? I must say, I _hate_ recursive symlinks.
> > >>
> > >> The advantage of using symlinks for kdisknav is that users can add
> > entries to
> > >> the kdisknav menu with simple drag&drop operations, without the need of
> > using
> > >> something like the KPanel menu editor. I argue that dragging stuff on a KFM
> > >> window (as the one the is shown to edit kdisknav menu entries) is easier
> > than
> > >> learning to use a menu editor. The drawback is that you must use "cp"
> > with the
> > >> -d option to copy symlinks as symlinks (as I wrote in the kdisknav doc).
> > >>
> > >> I understand your problem with symlinks, however. I'm thinking about an
> > >> alternative
> > >> solution.
> > >
> > >Which of the following options do you mean with -d?
> > >
> > >Usage: cp [-f] [-i] [-p] f1 f2
> > >       cp [-f] [-i] [-p] f1 ... fn d1
> > >       cp -r|R [-f] [-i] [-p] d1 ... dn-1 dn
> >
> > Under Linux you can call "cp" with the -d (= --no-dereference) option.
>   ^^^^^^^^^^^
> 
> So you say I have no way to copy my kdedir? That sounds a bit too
> limiting
> for my taste :)
> 

find /opt/kde -print | cpio -pdumv /path/to/new/kde

will work on any unix (OK, I don't have them all, "most?")

-- 
Peter

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