Re: avoiding wayland and pkgbase

you mean it would be better if it's only one package? well how about we have more than one set of those. plus ones you can create on your own. to me, it's actually good that i would be able to fully track all base files too. but there are multiple ways how one could distribute your system. plus you can change every part of it. you don't even need permission. only limitation would be attrib and you need to pick a new name if you do extensively change it. i think that installworld might as well run pkg to install stuff. i would keep all options open btw, if i were in charge somehow. and they even are. with ports, tho, i don't know if anyone runs their own tree that's pre pkgng? maybe ancient 4.* runners? but noone is going to remove installworld so far. btw i recalled ideas to remove src from dist, hopefully those don't catch on. would be bad for continuity. but yeah i get why there are all those concerns. but pkg is just way to track files. that part is perfect. the fact that it can now also bust your system on command, that's bit bad. unsure what answer is. who says one can't have base that's same, only it's files a tracked other way. i mean a package manager is glorified cp -av file / >> log; sha512 /file >> log after all. they got much more complex but that's essentially what they are. that in no way i does change what a fbsd base system is. tho one could argue that using less than full base would "dilute" the system off. unsure, i've been diluting my embedded systems for 10 years now. less build time too. i have all the src still tho. i could build or run all of it if i wish. what's the difference