rajkumar wrote:
Hi Shawn,
Initially the plan was to introduce a new attribute
named pkg.icon.24px in set action. But I think introducing a new action
type
is better than modifying the set action.
1. Modifying the set action for an attribute "pkg.icon.24px" and setting
the hash value is totally different from how the other attributes in
set action works. I think it is undesirable for set action to have two
different things, a opaque value and a filename/hashvalue. The set
action doesn't allow one to know to know if the value is a simple text
value or a filename/hashname.
2. pkgrecv would not know that the value of a set action is actually a
hash value that indicates a filename.
3. set action doesn't doesn't give the information about caching the
information in metadata area.
One advantage in using InfoAction is , we have the option of expanding
it in future to accommodate more data related to package.
For this reason I propose the InfoAction , which can be used for
pkg.icon.24px as of now and can be used in future for others data's without
any modifications to the code.
Note that those using the command line don't need the pkg.icon files.
I'd much rather that the pkg manager deal w/ such details rather than
the core packaging system, since this data is not really part of the
package, but rather it's description, and it's needed _before_ the
package is installed. Also, if someone devises a video-based
package manager, I don't want to add new actions to support their
need to find out what .avi files are appropriate to represent this
package in the current locale.
I'm very much of the persuasion that new actions should be introduced
only if needed to boot the system.
- 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
