Well, for now, just one machine running x11/gnome3 and a few other 'apps'. I still don't really understand how it all comes together so this is what I did.
On my builder machine:
I then used a syncing program to transfer files between the two machines. So:
Builder machine ----------------------------------- Old slow poke machine
/var/db/ports_synth_gnome3 = /var/db/ports
/var/synth/gnome3_packages = var/synth/live_packages
Only reason I used var/synth/live_packages because its existing on the old machine and I haven't removed synth from it yet.
On the builder machine I basically fed it a "just-build" lis which are the main ones, and a few leaf ports:
Synth fetched and built a very long list of ports. Then after completion I did
Before launching the build job on the builder machine I did a
So my question is why? Why would synth on the old machine still want to do a whole bunch of work right after the builder machine finished up? Where is my mistake? What other key source of info is missing so that the true state of the old machine is pulled into synth on the builder machine?
On my builder machine:
Code:
Synth configuration profile: GNOME3
===============================================================================
[A] Ports directory /usr/ports
(B) Packages directory /var/synth/gnome3_packages
[C] Distfiles directory /usr/ports/distfiles
[D] Port options directory /var/db/ports_synth_gnome3
[E] Build logs directory /var/log/synth_gnome3
[F] Build base directory /usr/obj/synth_gnome3
[G] System root directory /
[H] Compiler cache directory disabled
(I) Num. concurrent builders 4
[J] Max. jobs per builder 2
[K] Use tmpfs for work area true
[L] Use tmpfs for /usr/local true
[M] Display using ncurses true
[N] Fetch prebuilt packages trueI then used a syncing program to transfer files between the two machines. So:
Builder machine ----------------------------------- Old slow poke machine
/var/db/ports_synth_gnome3 = /var/db/ports
/var/synth/gnome3_packages = var/synth/live_packages
Only reason I used var/synth/live_packages because its existing on the old machine and I haven't removed synth from it yet.
On the builder machine I basically fed it a "just-build" lis which are the main ones, and a few leaf ports:
Code:
x11/xorg
x11/gdm
x11/gnome3
ftp/filezilla
games/minecraft-client
games/warsow
games/wesnoth
games/xonotic
www/firefox
x11/nvidia-driver-340
x11/nvidia-settingsSynth fetched and built a very long list of ports. Then after completion I did
pkg upgrade on the old machine. I got two unexpected results: (1) pkg used some of the packages made by synth, and it also fetched a fair few packages from FreeBSD. Which I thought hmmm okay. After it was all done I decided to run synth status on the old machine just as a check to see. To my surprise it said it would download 145 packages and build 14 packages.Before launching the build job on the builder machine I did a
portsnap fetch update on both machines at the exact same time, so both machines have the same ports tree. And the ports options directory are in sync.So my question is why? Why would synth on the old machine still want to do a whole bunch of work right after the builder machine finished up? Where is my mistake? What other key source of info is missing so that the true state of the old machine is pulled into synth on the builder machine?
