On 12/19/11 14:07, Brock Pytlik wrote:
On 12/19/11 08:46, Danek Duvall wrote:
Petr Cvachoucek wrote:
2) If the "dir" file is not a part of the package manifest, then it will
not be removed when the package is uninstalled (and I think it should
be).
If the directory in which "dir" sits is no longer delivered by any
package
on the system (as it probably ought to be if no package delivers any info
files), then that directory will be "salvaged" (stuck in
/var/pkg/lost+found), along with all its contents.
We've been talking about for ages about having a tag for a directory
saying
that anything left behind isn't worth salvaging, but have never come to a
conclusion on exactly how this should work.
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
Another option here which I've mentioned before would be to have "stub"
file actions. These actions wouldn't actually deliver a file but would
allow a package to indicate that it delivers a program/service which may
produce particular files. In addition to allowing us to remove those
files, it would also allow us to ensure that two packages don't both
think their programs will be creating the same files and verify that the
files produced have the right permissions/users/groups.
To add to that, you can accomplish today by simply including an empty
file in your package with preserve=true. That doesn't really have any
significant overhead compared to the stub action proposed.
The biggest problem with relying on declaring specific files is that
some programs create files whose specific names are not known at package
creation time.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
