Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=13400





------- Additional Comments From dkowis AT shlrm.org  2007-03-09 14:27 -------
(In reply to comment #10)
> My opinion hasn't changed... I asked my friend about hardlinks and he told 
> me 
> that he'd find that "ugly".
> Well, of course there is personal taste involved, but there is more info 
> for a 
> human in 
> 
> $ ls /etc/ldap.conf
> /etc/ldap.conf -> /etc/ldap/ldap-client.conf
> 
> than in 
> $ ls /etc/ldap.conf
> /etc/ldap.conf
> 
> I realize that I personally have something similar going. We have probs 
> with 
> the NIS server from time to time and for that I have 
> /etc/nsswitch.conf.local 
> and /etc/nsswitch.conf.nis for enabling/disabling NIS usage on my 
> workstation.
> I now copy the respective file to /etc/nsswitch.conf on demand, but it 
> would 
> be nicer if a simple ls could show me which config I have chosen atm (via 
> the 
> symlink target).
> 
> So, yes, my opinion still is that I'd like sorcery preserve my config 
> files, 
> even if they are symlinks. Also, concerning your "Two bits, four 
> combinations" 
> argument from comment #5, I see only two kinds of behaviour resulting from 
> the 
> two bits: reap or not reap. Of coruse one _could_ handle four cases, but in 
> this application the only bit that matters is the "is it a config file" bit.

I don't think that this is a really high priority bug. A simple workaround,
although "ugly", is a hardlink. It would work, and the spell isn't updated all
that often, so it should be fine. 

I do agree that something should be done about symlinks, but it will require
lots of thought and planning. We're talking about the core of the package
management stuff here. If this deleted the file the symlink pointed to, then
it'd be a big deal, but no data is lost. It is a fairly trivial task to 
recreate
this symlink on a recast of pam_ldap, which doesn't take long. It is perfectly
feasable for the admin to sit at the computer, cast it, then repair his 
symlink.
At least until a good solution is found to this.

Just my $0.02

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.