Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch

2008-07-31 Thread Alistair Crooks
On Tue, Jul 29, 2008 at 03:07:36PM -0700, Matthew Dillon wrote:
 :...
 :2. make replace - addresses the problems with make update by going
 :
 :3. pkg_rolling-replace - the nearest thing to automating this scheme.
 :
 :4. Use pkg_comp to build packages in a chroot environment, and then have
 :...
 :Hope that helps,
 :Alistair
 
 This brings up a pet peave of mine, which I wonder if the pkgsrc folks
 could address.
 
 Could you guys please make 'bmake help' actually print out something
 useful?  Like a summary of commonly used commands?  What it does now
 is really not very useful at all unless you are already a pkgsrc expert.
 
 (fetch-list, update, replace, pkg_rolling-replace, license stuff,
 package option commands, etc).
 
 It just drives me nuts, particularly when I'm trying to load up a new
 box and don't have a browser online, or when an update blows up my
 browser :-)

Yeah, a good point, and one I agree with completely - it's hardly
help if you need extensive background information to know what
to type.

I'll include [EMAIL PROTECTED] on this reply - the guys who did the
bmake help all read that list.  tech-pkg people - what do you think?

Thanks,
Alistair


Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch

2008-07-30 Thread Steve O'Hara-Smith
On Tue, 29 Jul 2008 14:53:14 +0100
Alistair Crooks [EMAIL PROTECTED] wrote:


 We don't have portupgrade, but there are a number of other ways of looking
 at the problem.
 
 1. make update - looks at all the packages installed, including

 2. make replace - addresses the problems with make update by going

 3. pkg_rolling-replace - the nearest thing to automating this scheme.
 
 4. Use pkg_comp to build packages in a chroot environment, and then have
 an install-binary-package fest.

Also my current favorite wip/pkgmanager which uses a want list of
packages works out what's changed and updates (with make replace), installs
and removes as necessary.

None of these work well with package renames though and build
failures can still cause problems (unlike portupgrade the old shared
libraries are removed by all of these mechanisms).

-- 
C:WIN  |   Directable Mirror Arrays
The computer obeys and wins.| A better way to focus the sun
You lose and Bill collects. |licences available see
|http://www.sohara.org/


Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch

2008-07-29 Thread Alistair Crooks
On Mon, Jul 28, 2008 at 12:12:29AM +0300, Cristi Magherusan wrote:
 Hello,
 On Sat, 2008-07-26 at 08:43 +0100, Alistair Crooks wrote:
  The pkgsrc-2008Q2 Branch
  
  
  The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2
  branch, which has support for more packages than previous branches. 
  As well as updated versions of many packages, the infrastructure of
  pkgsrc itself has been improved for better platform and compiler
  support.
 
 Congratulations and many thanks to everyone who contributed!
 
 For the future releases, do you have any plans to include an officially
 supported tool that will properly update/rebuild all or some of the
 installed packages on a system, without removing everything and
 rebuilding from scratch, while still maintaining the binary consistency
 of the system? I'm thinking at something like the portupgrade tool from
 FreeBSD.

We don't have portupgrade, but there are a number of other ways of looking
at the problem.

1. make update - looks at all the packages installed, including pre-reqs,
deletes the outdated packages, and attempts to build them all again. This
can leave you without a working package if the build fails for any reason.
Caveat return-presser.

2. make replace - addresses the problems with make update by going
through all the pre-reqs to find out of date packages, and builds the
out of date one. When it's built, a copy of the old package is kept,
the old package is deleted, the new one installed, and all references
are fixed up. This may not DTRT if a shared library bumps the major
number. It is accompanied by a warning that data loss may ensue just
in case of the major number bump.

3. pkg_rolling-replace - the nearest thing to automating this scheme.

4. Use pkg_comp to build packages in a chroot environment, and then have
an install-binary-package fest.

In passing, note that pkgsrc numbering scheme is logical, and increasing,
and so we can do , =, , = matching for things like audit-packages,
calculation of down-level packages etc

Hope that helps,
Alistair


Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch

2008-07-29 Thread Matthew Dillon
:...
:2. make replace - addresses the problems with make update by going
:
:3. pkg_rolling-replace - the nearest thing to automating this scheme.
:
:4. Use pkg_comp to build packages in a chroot environment, and then have
:...
:Hope that helps,
:Alistair

This brings up a pet peave of mine, which I wonder if the pkgsrc folks
could address.

Could you guys please make 'bmake help' actually print out something
useful?  Like a summary of commonly used commands?  What it does now
is really not very useful at all unless you are already a pkgsrc expert.

(fetch-list, update, replace, pkg_rolling-replace, license stuff,
package option commands, etc).

It just drives me nuts, particularly when I'm trying to load up a new
box and don't have a browser online, or when an update blows up my
browser :-)

-Matt
Matthew Dillon 
[EMAIL PROTECTED]


Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch

2008-07-28 Thread Joerg Sonnenberger
On Sun, Jul 27, 2008 at 07:21:21PM -0400, Constantine A. Murenin wrote:
 Or like `pkg_add -u` on OpenBSD? :-)

When did you last read the pkg_add man page coming with pkgsrc? :)

Joerg


Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch

2008-07-27 Thread Cristi Magherusan
Hello,
On Sat, 2008-07-26 at 08:43 +0100, Alistair Crooks wrote:
 The pkgsrc-2008Q2 Branch
 
 
 The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2
 branch, which has support for more packages than previous branches. 
 As well as updated versions of many packages, the infrastructure of
 pkgsrc itself has been improved for better platform and compiler
 support.

Congratulations and many thanks to everyone who contributed!

For the future releases, do you have any plans to include an officially
supported tool that will properly update/rebuild all or some of the
installed packages on a system, without removing everything and
rebuilding from scratch, while still maintaining the binary consistency
of the system? I'm thinking at something like the portupgrade tool from
FreeBSD.

Best regards,
Cristi



Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch

2008-07-27 Thread Constantine A. Murenin
On 27/07/2008, Cristi Magherusan [EMAIL PROTECTED] wrote:
 Hello,

 On Sat, 2008-07-26 at 08:43 +0100, Alistair Crooks wrote:
   The pkgsrc-2008Q2 Branch
   
  
   The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2
   branch, which has support for more packages than previous branches.
   As well as updated versions of many packages, the infrastructure of
   pkgsrc itself has been improved for better platform and compiler
   support.


 Congratulations and many thanks to everyone who contributed!

  For the future releases, do you have any plans to include an officially
  supported tool that will properly update/rebuild all or some of the
  installed packages on a system, without removing everything and
  rebuilding from scratch, while still maintaining the binary consistency
  of the system? I'm thinking at something like the portupgrade tool from
  FreeBSD.

Or like `pkg_add -u` on OpenBSD? :-)

http://www.openbsd.org/faq/faq15.html#PkgUpdate
http://www.openbsd.org/papers/ven05-espie/

br,
cnst.su.