Just for clarity: In your upgrade procedure, are you uninstalling the package and then installing it again, or are you simply installing the new version on top of the old?
ramanujan oops wrote: > "but if you make customizations, it will leave the file alone." > > - Does Customizations here refer to changing the attributes of the file > or the contents of the file? > > Because, I edited the old version of the file and added a few more lines > of data to it before adding the files into the newer version of my > package and had set a 'preserve' attribute to it too. But still, when I > installed the new package, my old file was overwritten. > > The basic need here is to retain old/new file and discard the other file > file based on some constraint (as documented by the 'renameold', > 'renamenew', 'strawberry' options). However, I'm not able to achieve > that functionality. Request you to kindly throw some light here. > > Appreciate your patience and support.. > > regards, > Ram > > On Fri, Oct 31, 2008 at 9:31 PM, Danek Duvall <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > The problem is that you haven't made any changes to the file. pkg(5) > assumes that you want the file as delivered in the package, but if > you make > customizations, it will leave the file alone. There's no good way > to tell > whether the user wants to keep the file as it was originally > delivered or > whether she wants to use whatever the package delivers. > > Danek > > > > ------------------------------------------------------------------------ > > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
