On Tue, Jun 10, 2014 at 07:32:56PM +0200, Lennart Poettering wrote: > Symlinks should probably just be considered different type of file, that > have a contents and stuff. The contents is usually a file name, and > there's a size limit, but other than that it's just a magic kind of > file, where the symlink destination is the conents. That's how git > handles this, for example. > > I have the suspicion that this is really something to fix in your > package manager. It should learn to handle symlink upgrades the same way > as configuration file upgrades....
Does rpm handle this exact case? Can anyone comment on dpkg handling of this case? > > > I mean, ideally we'd just invoke "systemctl preset" for these things, > > > but for the sake of cross-compilation we can avoid this easily. > > > > > > We probably should ship make sure to ship the very same symlinks we > > > create with "make install" with a preset file though... > > > > Yeah, this sounds prone to drift unless it could be generated from some > > "master" list. > > Well, given that it's not a hundred symlinks, but just a few, I think > having a list in the preset files and one in the makefile isn't too > error-prone... But it still involves humans. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
