[csw-users] Release schedule for stable packages

Mark McCoy Mark.McCoy at utsa.edu
Wed Nov 9 15:00:25 CET 2005

By "cherry picking", I was referring to having a current pkgsrc tree
checked out alongside the 2005Q3 tree and building updated packages for
security reasons out of that (presumably the pkgsrc system is smart
enough to pull in proper dependencies for this type of update).  I
haven't looked into how the netbsd pkgsrc team handles security updates,
though.  They might already do something like this and issue patches to
their stable tree.

-----Original Message-----
From: users-bounces+mark.mccoy=utsa.edu at lists.blastwave.org
[mailto:users-bounces+mark.mccoy=utsa.edu at lists.blastwave.org] On Behalf
Of James Lee
Sent: Wednesday, November 09, 2005 3:42 AM
To: questions and discussions
Subject: Re: [csw-users] Release schedule for stable packages

On 07/11/05, 21:21:00, Mark McCoy <Mark.McCoy at utsa.edu> wrote regarding 
[csw-users] Release schedule for stable packages:

> This allows an admin to standardize on, for example, the 2005Q3 
> packages, and allows "cherry picking" of packages for security updates

> from a later tree.

When you're cherry picking make sure you don't get a rotten apple.

If you add a package to stable from unstable check if you need to add
its prerequisite and *supported* packages too, then repeat for any
additional packages needed.  You might be able to add parts of the
package tree but please understand that it won't always work unless a
connected group is updated.  Unless you are prepared to verify each
package in the chain the group is going to be large or unverified which
nullifies your initial reasoning of doing it for security.

users mailing list
users at lists.blastwave.org

More information about the users mailing list