freebsd stable - Mar 2014 - [HEADSUP] pkg 1.3.0 alpha1: Breath of fresh air from Kirov

Hello,

I'm really pleased to announce that the release process for the new major
version of pkg(8) has started with this first alpha1 release.

The main feature for this release is the complete rework of the solver.
pkg(8) now features a real SAT solver and uses it for every operations requested
by the user that may add, upgrade or remove packages.

This work is is the result of the very succesfull Google Summer of Code 2013, by
Vsevolod Stakhov (vsevolod@ also known as cebka). This is a major improvement
for the project, and the fundation for lots of new features in the future.

I would like to thanks Vsevolod for all the new ideas and hard work he has done
(not limited to the new solver.)

Back to the release now. pkg 1.3.0 comes with the following new features:
- New solver that can support external solvers using the CUDF format and the
  internal SAT solver
- pkg-ssh(8) is now sandboxed using capsicum if available
- pkg-ssh(8) now uses poll(2)
- Remove StringList usage to improve portability
- Rework the build system to using autotools to help portability
- Now fetching is done to a temporary location and cleaned up if it fails
- Remove support for PACKAGESITE
- pkg-audit(8): remove support for portaudit compact database (only VulnXML will
  be used)
- Improved UI experience based on jmmv write up
  (http://julipedia.meroh.net/search/label/cli-design)
- Hide the average speed from the progress bar (confusing for users)
- Reworking the database locking mechanism into a finer grain and more clever
  system
- Dynamic conflict handling if a conflict on files is detected at the sanity
  check level, try to solve the problem again with the new conflict information
- Fix %t (timestamp) modifier in pkg_printf(3)
- pkg-info(8): full output now has a new field "date installed"
- New pkg -o A=B to overwrite configuration from command line without the need
  of defining environment variables
- pkg-install(8): can handle local files
- pkg-add(8) is now an alias on pkg-install
- Simplify API by using more and more libucl objects (hidden behind an opaque
  'pkg_object')

Thanks to everyone that has contributed code for this release:
Alberto Villa, Alexandre Perrin, Baptiste Daroussin, Brad Davis, Bryan Drewery,
Jamie Landeg Jones, John Marino, Matthew Seaman, Maximilian Ga?, Michael
Gehring, Michael Gmelin, Rodrigo Osorio, Rui Paulo, Sean Channel, Stanislav E.
Putrya, Vsevolod Stakhov, Xin Li, coctic

Thanks also to all people reporting bugs, sharing ideas, testing and using
pkg(8).

regards,
Bapt

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140317/a6657b15/attachment.sig>

Looks great! Thanks as always for the work. I do have one question (below).

On Mar 17, 2014, at 11:21 AM, Baptiste Daroussin <bapt at freebsd.org>
wrote:
> - Remove support for PACKAGESITE
There are two cases where I still define PACKAGESITE in the environment,
specifically when building new jails or VM images. Can you suggest alternatives?

1. Installing/bootstrapping the latest pkg from a specific source. Often I build
in an environment that is firewalled from the Internet at large but I have a
local repo. (And it's nice to know exactly what version with which options
I'm installing.)

2. Installing a package that includes a repo file for my local custom repo. This
is a chicken-and-egg problem for which PACKAGESITE was a nice solution since
there's no risk of a stale repo file being left behind--either the package
is installed (with the correct/current repo file) or it isn't.

JN

Looks great! Thanks as always for the work. I do have one question (below).

On Mar 17, 2014, at 11:21 AM, Baptiste Daroussin <bapt@freebsd.org> wrote:
> - Remove support for PACKAGESITE
There are two cases where I still define PACKAGESITE in the environment,
specifically when building new jails or VM images. Can you suggest alternatives?

1. Installing/bootstrapping the latest pkg from a specific source. Often I build
in an environment that is firewalled from the Internet at large but I have a
local repo. (And it's nice to know exactly what version with which options
I'm installing.)

2. Installing a package that includes a repo file for my local custom repo. This
is a chicken-and-egg problem for which PACKAGESITE was a nice solution since
there's no risk of a stale repo file being left behind--either the package
is installed (with the correct/current repo file) or it isn't.

JN

_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"

On Mon, Mar 17, 2014 at 11:40:52AM -0600, John Nielsen
wrote:
> Looks great! Thanks as always for the work. I do have one question (below).
> 
> On Mar 17, 2014, at 11:21 AM, Baptiste Daroussin <bapt@freebsd.org>
wrote:
> 
> > - Remove support for PACKAGESITE
> 
> There are two cases where I still define PACKAGESITE in the environment,
specifically when building new jails or VM images. Can you suggest alternatives?
> 
> 1. Installing/bootstrapping the latest pkg from a specific source. Often I
build in an environment that is firewalled from the Internet at large but I have
a local repo. (And it's nice to know exactly what version with which options
I'm installing.)
What is done in the FreeBSD DVD is creatign a conf files manually:
local: {
	url: "http://where"
}

and env REPOS_DIR=/path/to/the/directory/containing/the/file pkg
...
> 
> 2. Installing a package that includes a repo file for my local custom repo.
This is a chicken-and-egg problem for which PACKAGESITE was a nice solution
since there's no risk of a stale repo file being left behind--either the
package is installed (with the correct/current repo file) or it isn't.
same as above or if you already have pkg bootstrapped you can do pkg add
http://...../yourpkg.txz
which makes me see that 1.3.0.a1 has lost pkg add|install http://... which we
need to fix for alpha2

Thanks for the first bug report. :)

regards,
Bapt

On 18 March 2014 06:21, Baptiste Daroussin <bapt@freebsd.org> wrote:
> Hello,
>
> I'm really pleased to announce that the release process for the new
major
> version of pkg(8) has started with this first alpha1 release.
>
> The main feature for this release is the complete rework of the solver.
> pkg(8) now features a real SAT solver and uses it for every operations
> requested
> by the user that may add, upgrade or remove packages.
>
>
I am sure this has been discussed before but does this release do anything
to help automating UPDATING or is this a planned feature?

Taking the last entry which says to "pkg set -o
misc/p5-OSSP-uuid:misc/ossp-uuid-perl", just do it for me pkg!


Andrew
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"

On 18 March 2014 06:21, Baptiste Daroussin <bapt at freebsd.org> wrote:
> Hello,
>
> I'm really pleased to announce that the release process for the new
major
> version of pkg(8) has started with this first alpha1 release.
>
> The main feature for this release is the complete rework of the solver.
> pkg(8) now features a real SAT solver and uses it for every operations
> requested
> by the user that may add, upgrade or remove packages.
>
>
I am sure this has been discussed before but does this release do anything
to help automating UPDATING or is this a planned feature?

Taking the last entry which says to "pkg set -o
misc/p5-OSSP-uuid:misc/ossp-uuid-perl", just do it for me pkg!


Andrew

On Tue, Mar 18, 2014 at 01:57:51PM +1300, Andrew Thompson
wrote:
> On 18 March 2014 06:21, Baptiste Daroussin <bapt@freebsd.org> wrote:
> 
> > Hello,
> >
> > I'm really pleased to announce that the release process for the
new major
> > version of pkg(8) has started with this first alpha1 release.
> >
> > The main feature for this release is the complete rework of the
solver.
> > pkg(8) now features a real SAT solver and uses it for every operations
> > requested
> > by the user that may add, upgrade or remove packages.
> >
> >
> I am sure this has been discussed before but does this release do anything
> to help automating UPDATING or is this a planned feature?
> 
> Taking the last entry which says to "pkg set -o
> misc/p5-OSSP-uuid:misc/ossp-uuid-perl", just do it for me pkg!
> 
The new solver takes care of this without the need of pkg set -o :)
It would be now transparent for users. (all they might discover is that a
conflict is detected then a new pass in the solver is needed and and the
problems is solved properly by the removal of ossp-uuid-perl and installation of
p5-OSSP-uuid.

regards,
Bapt