The info action is designed to allow the package to include any
file-based meta data, not just icons. So whether packages have video
clips or ring tones or other ways to present themselves, the info action
can be used for that with just a different value for type. Another new
action would not be needed for that.
Earlier, we proposed a solution that would use only set and file actions
to allow delivery of icons in a package for use by GUI tools. But
several on the list correctly pointed out the inefficiencies of doing it
that way. For the reasons listed by Rajkumar, using only a set action
with publishing modifications doesn't work very well either. If you
have a suggestion for a design by which a GUI tool could support icons
for packages without adding a new action, I'd be interested in hearing it.
Thanks.
Tom
Bart Smaalders wrote:
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
begin:vcard
fn:Tom Mueller
n:Mueller;Tom
org:Sun Microsystems, Inc.;Update Center Software
adr:;;21915 Hillandale Dr;Elkhorn;NE;68022;USA
email;internet:[email protected]
title:Senior Staff Engineer
tel;work:877-250-4011
tel;fax:877-250-4011
tel;home:402-916-9943
x-mozilla-html:TRUE
version:2.1
end:vcard
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
