I'm sure some of the things below are just a lack of me missing it in 
the documentation or simply not knowing what I'm doing because I'm new 
to OpenSolaris..

1) After you pkg verify and realize that something isn't correct.. 
what's the best way to fix it?
    a. Should something like pkg verify -fix be added so you can 
optionally fix the package
    b. pkg restore/reinstall which will basically override any changes 
which have been made.. (deletions, modifications.. etc)
    c. Try to manually fix the package

2) Unlike Linus.. I feel sysadmins should know and be able to treat 
packages containing security updates at a higher priority.
I'm currently monitoring
http://blogs.sun.com/security/feed/entries/rss

and cross referencing the notes there to what's available in pkg 
update-image -nv.. I'm sure there info is in a central database.. could 
that somehow be tied into pkg or a tool which is aware to check if there 
are any affected packages and optionally take some course of action like 
install an update. (This idea is directly stolen from other distributions)

3) How will packages nearing eol be handled?

4) Some things which I think would be great to have in the 
metadata/somewhere

    a. which build options were used to make the package
    b. *URI to the source..
    c. The most restrictive license type.. pkg info --license  is great, 
but something simple like CDDL, GPL2.. etc..

* From ( http://dlc.sun.com/osol/docs/content/IPS/ggdvj.html ) I see 
source_url, but I'm not sure where this is stored.. I don't see it in 
pkg info.. Is it just optional and not being provided?

5) Is there a proper way to change the dependency for a virtual package?

pkg info slim_install
          Name: slim_install
       Summary: slim install cluster
         State: Installed
     Authority: opensolaris.org (preferred)
       Version: 0.1
 Build Release: 5.11
        Branch: 0.96
Packaging Date: Fri Aug 29 15:12:56 2008
          Size: 0 B
          FMRI: pkg:/[EMAIL PROTECTED],5.11-0.96:20080829T151256Z

pkg contents  slim_install
PATH

In this case would I have to modify
/var/pkg/pkg/babel_install/0.1%2C5.11-0.96%3A20080825T195126Z/manifest

6) Small nit..
 From the man page

image-update [-fnvq]

"With the -f option, skip safety  checks."

, but from the --help menu

pkg image-update [-nvq]

and online doc
http://dlc.sun.com/osol/docs/content/IPS/cmdref.html

At some point I plan to dive into the source.. Any recommendations on 
tooling.. vim or give the Netbeans python support a try?

Thanks and hopefully I don't ruffle any feathers with this..

./C
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to