@
Trihexagonal: Concerning so-called
port"master", read the
poudriere howto &
don't use it. No it's not a bad thing to teach users to build
ports(7) themself, but that's advanced usage & not for the average non-
nerd. As usual, there are exceptions
e.g. when it's neccessary to build the
drm-*-kmod
, of course it's perfectly ok to build that on the host unjailed without
synth(1) or
poudriere(8), since they do not have any dependencies. For those who are eager to learn & dive into how an OS & programming works, it's an invaluable experience to build kernel & world & apps, yes. But for the average
user? No, I don't think so.
They don't come much closer to non-average nerd than I do. That's the point of me telling about my less-than-average-person-here seat time in an Official Classroom. I didn't take the GED course either, just the test.
Some 15 year old boy dying of cancer that wanted his High School Diploma before he died beat me out for top score for tests taken that year at that facility at the last minute. He never sat in a class seat either, or was there to accept his Honor as Class Valedictorian. I can't really complain, I was Salutatorian.
Now I have to embarrass myself... I've never used a jail or built a kernel and only have minimal experience with ZFS when I tried out DandyOS, Trident or whatever they were calling it that week.
In fact, I've never had to go through anything but the following to get the Master of Ports to do my bidding. Not that there's anything wrong with the Tutorial at all. But it's a lot of work I don't ever have to:
jitte@jigoku:/ $ su
root@jigoku:/ # cd /usr/ports/ports-mgmt/portmaster
root@jigoku:/usr/ports/ports-mgmt/portmaster # make install clean
root@jigoku:/usr/ports/ports-mgmt/portmaster # cd /
root@jigoku:/ # portmaster security/rkhunter
And we are up and rolling on to X, fluxbox, etc. easy as that.
I suppose the reason I don't need it is from here on down:
"Why is poudriere needed in the first place? The ports infrastructure suffers from numerous design faults that are not easy to overcome without a package building tool like poudriere. These faults include:
Building of ports as outlined in
ports(7) is performed on the live system. Many build failures stem from this when an already installed port or leftover files from an old version causes conflicts with the to be built new version of the port....."
I only build on live systems sitting in front of me in my own home and that kind of build failure is the experience I have to solve but can't teach others, as previously mentioned.
As far as being told why not to use it in your link, you are making a lot of assumptions there:
VladiBG said:
I don't agree with above statement.
I'm using FreeBSD from RELEASE 6.0 and back then there was no
portmaster script to help you upgrade your ports. [...]
You don't have to, because this is not a question of agreement, but right and wrong."
And here. First of all, you don't use
ports-mgmt/portmaster like I do, and likely the source of your frustration with something that doesn't work for you that works like a charm for me and I love to use:
portmaster -F x11/kde5
(recursively fetch all distfiles needed to build kde5)
The result is that after more than one hour of uselessly processing the dependency graph, this self-called
master still fetches
nothing.
This will do the job, pull in a list of all dependencies it deems necessary for the build, then present them to you for authorization to proceed, or options should you not want to install everything it shows. I go with it unless it's something like IPV6 I've disabled or something I know to watch for to disable during the time it's presented to me.
root@jigoku:/ # portmaster x11/kde5
At the end of that process it will present the full list of dependencies to be pulled in during the build as my faithful servant who I place full trust in. If I'm satisfied with it go to it. If I don't want to install all of the programs presented in the list I can say no and it will give me the option to get picky.
Then once given the Master of the Master of Ports nod of approval it pulls in dependencies to be built as needed during the build and I sit in the recliner and listen to my W520 .mp3 player through headphones while it toils.
I'll stick with what I like to use and my Tutorial will continue to use ports once again after being told countless times why it shouldn't. When I need told what's right and wrong I'll consult my moral compass, soon as it stops spinning like a manic merry-go-round on meth...if ever.
I'll rely on Sir Dice till then, though he doesn't think I should use ports either I trust his judgement.