Liane Praza wrote:
[email protected] wrote:
I looked through the ON pieces in detail, and didn't see anything glaring anywhere else.

Thanks for the review.

SUNWps
 - I'm presuming this chattr goes away in 129?  It looks like the
   ON package in now has this file due to the fix for 6885330.

I believe we need to keep the chattr going forward as the ownership of
this editable file has changed from SUNWpc to SUNWps.

Hm.

Can you give me (or point me to someone who can give me) the big theory statement about this?

Do we always have to track editable file movement between packages? For how long does this data have to be maintained? How about across multiple moves. Renames? Obsoletes?

Clearly there's policy I wasn't accounting for previously. :/


If you want upgrade to work (eg editable files that move in either
package or file path (from SUNWcs:/etc/foo to something like
really/cool/new/pkg/name:/etc/bar, you'll need to add a tag (once)
to the file specifying it's original name and package:

From the fine man page pkg(5):

 original_name This attribute is used to handle editable files moving
               from package to package or from place to place, or both.
               The form this takes is the name of the originating package,
               followed by a colon and the original path to the file.
               Any file being deleted is recorded either with its
               package and path, or with the value of the original_name
               attribute if specified.  Any editable file being installed
               that has the original_name attribute set will use the
               file of that name if it is deleted as part of the same
               packaging operation.


--
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

Reply via email to