Miroslav Lachman wrote:
It is not just about updates but about new installs too - if you have
dozens of machines for customers and you need them all in the same
version. Then some customer need some package not installed on his
machine and you cannot run "pkg install somepackage" because then you
will end up with upgrade of already installed packages (dependencies)
before new package from current quaterly branch is installed.
(I do not use this scheme, but I understand the environment where
somebody needs frozen pkg repo for much longer time than 3 months)
Create your own snapshot... it has 2 immediate and distinct advantages:
1/ Its frozen across all your systems (which means when random updates
on how the ports system works are applied breaking everything you're not
affected.)
2/ You can apply patches (security patches) as you need them instead of
having to upgrade/re-snapshot because the port manager refuses/ignores
requests to update the previous snapshot (the one you settled on)..
Then when all that is done, you can do as I did, fork the entire lot
into a secure, up to date and working tree/build system (for OS and
ports) where you actually have a working and reliable production system
rather than a moving target... then you can remove all the bloat and
unnecessary crap from the base OS and replace it all with ports stuff so
that the base OS doesn't need upgrading unless there is a
libc/kernel/etc security issue... Oh wait - that's exactly what I did
as well... you get the idea.. don't argue for it, just do it yourself
its a lot less of a waste of energy and you get exactly what you want/need.
Regards,
--
Michelle Sullivan
http://www.mhix.org/
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
