On Wed, Dec 16, 2015 at 11:15:29PM +0000, Tati Chevron wrote:
> >Or both. Drop VMWare on the floor NOW, if you need virtualisation use
> >generic QEMU/KVM in any recent Linux distribution of your choice and
> >plan to wipe it clean after you're done fiddling with it. Yes, really
> >seriously remove the virtualisation for a build machine, go bare metal.
> >Try without hyperthreading for a comparison. Before you notice and get
> >to complain you need VM for something just use the native OpenBSD
> >hypervisor.
>
> Our build machines both run on bare metal. To be honest, once you've
> pulled the entire set of source distfiles for one release, you don't even
> need much in the way of connectivity to stay up to date.
>
Virtual is the only option but I'm not trying to mirror the entire ports
collection. I'm trying run a puppet/package server for a tiny fleet of
soekris boxen.
> From the way the OP described the setup, it does look like he intends to
> run the build machine remotely, as a VPS. I wouldn't recommend using a
> VPS as a build machine, as you need CPU and RAM with little connectivity,
> which is the opposite of what most VPS providers will offer. Our build
> machines are on-site, and we just send the resulting binary packages
> wherever they need to go.
>
It's not remote. It runs as one virtual server of two on a 2010
MacPro. My host is modest. It's a 2.8GHz Zeon with 24Gb of RAM and
0.5Tb of SSD. My ports list is equally modest. I generally run OpenBSD
as a server role. If I were to build an OpenBSD desktop, I would rely
on project's mirrors. There's a good argument to be made that me using
dpb is a fools errand but I like to rely on myself. My ports list is
equally modest at 24 ports right now. I expect it to grow but not by much.
> >>Also, be aware that some ports have a mass of unnecessary dependencies,
> >>and that tweaking this can reduce the build time substantially, especially
> >>if you are building the same packages repeatedly for some reason.
> >
> >Use a "virtual" axe ;-) virtually "axing" around.
>
> Really, have a look at the dependencies for ImageMagick, and ask yourself
> who really uses djvu, for example. Removing it and ghostscript reduces
> the dependencies from:
>
> 5.8-release:
>
> # make print-build-depends
[ massive dependency list snipped... ]
Thank you!!! This hits the nail on the head. One of the twenty four
things I currently want is editors/emacs,gtk2. That wants ImageMagick... I
stopped the dpb build this morning at I=417 ports. As far as I'm
concerned that's off the chain. I'm trying to decide between figuring
out who the big players are in my dependency chain or just going with
editors/emacs,no_x11 and using tramp and or git when I want bells and
whistles emacs.
--
Chris
__o "All I was trying to do was get home from work."
_`\<,_ -Rosa Parks
___(*)/_(*)_____________________________________________________________
Christopher Sean Hilton [chris/at/vindaloo/dot/com]
