[ProgSoc] Debian policy question - opinions sought

[jedd <jedd@nospam.progsoc.uts.edu.au>]

 Howdi,

 If I do a recursive scp of a debian box's /etc directory, it gets into
 a really ugly loop when it reaches /etc/apache.  The /etc/apache/conf
 symlink (which points to . ) causes it to dig deeper and deeper into
 the same directory, until it carks it.  Which takes a surprisingly long
 time, actually.

 I checked with the debian maintainer of the package, and he simply
 said that I should fix my program (in this case openssh's scp binary),
 and that it would break policy, and referred me to :

 http://www.debian.org/doc/debian-policy/ch-files.html#s11.5

 But on reading that, I'm not sure that the suggestion to effectively do :

 cd /etc/apache
 ln -s /etc/apache conf

 .. is somehow unacceptable in the policy, as compared to the current :

 cd /etc/apache
 ln -s . conf

 I'm not going to win a battle I don't want to fight with a Debian 
 maintainer, and I'm equally as unlikely to go tell the nice openSSH
 people that their software is broken.  But I'm nonetheless unconvinced.

 I'm thinking that the other approach that isn't *too* ugly (for my
 original problem) is to ssh a tar cvf call, then scp that file back,
 then untar it locally.  I'm less interested in reasons why I wouldn't
 want to keep a local copy of configuration files from a set of machines
 on a single box.

 Jedd.
-
You are subscribed to the progsoc mailing list. To unsubscribe, send a
message containing "unsubscribe" to progsoc-request@nospam.progsoc.uts.edu.au.
If you are having trouble, ask owner-progsoc@nospam.progsoc.uts.edu.au for help.