Brock Pytlik wrote: > I found this very clear and liked the examples. > > Bart Smaalders wrote: >> [snip] >> Another common problem is moving files, links and directories around >> the filesystem and between packages; this is often handled via >> scripting in the case of SVr4 packages. In IPS, normal (not editable) >> files can simply move between packages; this results in their removal >> from the original location and then their re-installation in their new >> location. To insure that editable files retain their customizations, >> the receiving package must annotate the action that deliver the new >> file name/location with an attribute that defines the original owning >> packages and location. This looks like this: >> >> original_name=SUNWfoo:etc/foo.txt >> >> indicating that the name of original owning package was SUNWfoo and >> that the original path was etc/foo.txt. Note that no matter where >> this file moves to subsequently, it should always maintain this >> identifier. >> > I feel like I have to ask what happens if the SUNWfoo:etc/foo.txt gets > moved to SUNWbar:etc/bar.txt, then to SUNWbaz:etc/baz.txt, and then to > SUNWfoo:etc/not_foo.txt > > Is each action tagged with a reference to the previous location, or to > the original, or to the transitive closure? >> [snip]
Once the original_name attribute is set, it never changes. In this manner, the file is correctly upgraded, even across multiple intervening moves/renames. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
