On Thu, 8 Feb 2001, Alistair Crooks wrote:
> Yes, I know this is what you do at the moment.  But I don't want to
> install ssh or cvs separately - I want them to be installed from the
> pkgsrc framework.  I don't want to think:  am I on a bulk build box? 
> Do I have to install this in a non-standard place?  Are my keys going
> to get nuked?  before I do anything. I just want it to work. 

FYI, ssh and cvs are installed via pkgsrc *of course* in the bulk
builds. dito for perl after the builds:

( cd lang/perl5-base ; make bulk-install )
etc.

And you sure know that our ssh pkg never did nuke any keys.



> Which
> is why I'd like there to be a list of packages which shouldn't be
> knobbled, and why I think ssh and cvs (if appropriate i.e.  in pkgsrc)
> should be on that list.  I don't want the list to be huge, because you
> then run the risk of missing a pre-requisite package.

Er, and things like kdevelop and whatnot that can use cvs will just
silently pick it up and do things with it, without a dependency being
detected. that's not the idea of the bulk builds.


> > this is why so far only xpkgwedge comes to mind since it has a big effect
> > on the pkgs being built.
> 
> No, I can't think of any other package that influences the way that
> pkgsrc itself behaves, either.

Maybe compilers (on solaris)?


 - Hubert

-- 
Hubert Feyrer <hubert.feyrer@informatik.fh-regensburg.de>