On Sun, Sep 07, 2008 at 08:56:21PM +0200, "C. Bergstr?m" wrote:
> 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
See
388 pkg command needs a "fix" subcommand or similar
> 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)
Eventually, we plan on having a stream of change that you can "subscribe"
to (i.e., that's what's published at a particular URL, and the origin of
your primary authority would point to that) which is security fixes only,
or some other high-reward, low-volume stream. For now, though, you have to
do the coordination by hand.
> 3) How will packages nearing eol be handled?
Features being EOLed go through an existing architectural and business EOL
process. Eventually, we'll have an EOL process for packages. See
345 Package rename mechanism should support EOL, Interrupt
> 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..
Search for "Tags and attributes" in the pkg-discuss mail archives. Or bug
Stephen to actually publish the damned thing -- I don't seem to have any
influence there. It mentions several package attributes related to the
source and being able to rebuild it.
> * 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?
None of those attributes are in use yet, and all will have different names
by the time we do start using them.
> c. The most restrictive license type.. pkg info --license is great,
> but something simple like CDDL, GPL2.. etc..
Yeah. Each license action has a "license" attribute which intended for
exactly this purpose. Unfortunately, we're currently populating it with
useless values, and doing a better job hasn't been a high priority.
> 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
I'm not sure what you're asking for here. Could you clarify?
> 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]
That's a bug -- it should be mentioned in the usage message. Please file a
bug (Development/pkg/cli).
> and online doc
> http://dlc.sun.com/osol/docs/content/IPS/cmdref.html
This tends to be a bit behind, but it's targeted at the major milestone
releases (2008.05, 2008.11, etc), rather than the intermediate builds,
which is where -f showed up.
> At some point I plan to dive into the source.. Any recommendations on
> tooling.. vim or give the Netbeans python support a try?
I use vim, quite happily. A couple of the guys on the team use emacs, and
I don't think anyone uses netbeans.
> Thanks and hopefully I don't ruffle any feathers with this..
Not at all.
Thanks,
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
