Indeed I have, Bob. But there were some issues afterwards. You may want to see my message here.
BTW, I am not much younger or sharper . . . well, at least not as young as most as the other guys and gals posting here.
Sorry for asking too many questions
Ok. Just woke up and the café is kicking in.Blasphemer! Away with you!
Not exactly sure what that means, but I'll check it out. To be honest, I haven't tried any of his methods or tools, I suppose because I am already comfortable with using dosdude1's tools, which have worked well for me. As they say, don't change horses in the middle of the stream, and if it ain't broke, don't try to fix it.
PS: Okay, now I am going to be lazy as well . . . Exactly how do I access this "enterprise-like distribution system"?
$softwareupdate --clear-catalog$softwareupdate --help
Oh gosh . . . Okay . . . I quickly figured it out when I went back and read what you and foxlet had posted earlier.
I now realize that I don't even need those two catalog files that were downloaded when I clicked on those two links . . . although I am wondering what would happen if I were to place them, say, in my Home folder, and then use a local path in that first command string, instead of his web server URL.
Even if it were to work, there is really no advantage in it, I suppose, being as the App Store would still need to connect to his server in order to actually download the install packages themselves.
I must say though, that after seeing how this works, I can see why you have been raving about it so much. It is obviously a lot easier than dosdude1's patch tools method, if one doesn't mind typing a few commands in the Terminal to get the ball rolling. I mean, oh gosh . . . no patches required? And your unsupported machine recognized? What more can we ask for?
So if I understand this correctly, the way that this works is that after changing Apple's default public catalog to the catalog on foxlet's web server, Software Update is automatically set to check his server for updates, instead of Apple's servers, and if there are updates, to enter them in the App Store app. The updates are then downloaded from his server as well.
So can you verify that this is in fact an automated process, and that those three command strings only need to be entered into the Terminal one time in order to get things started?
I mentioned earlier that I would need some compelling reason to switch from dosdude1's method to foxlet's method. Well, I would say that this ease of use -- without the necessity of us personally applying patches and post installs is a pretty compelling reason to switch.
I bet you just loved reading that last line.
In looking at the two methods, I suppose what it really comes down to are two primary issues:
1. Trusting dosdude1 and foxlet to be honest gentlemen who will do nothing to compromise our machines by injecting malicious or dangerous code into their patches.
2. Trusting and hoping that dosdude1 will not tire of updating his patches, and trusting and hoping that foxlet will not tire of updating his catalogs, and keeping the latest builds on his web server.
Yes, I am really thinking this issue through.
So now the big, BIG question: Why did you two -- pkouame and foxlet -- have to dangle this new carrot in front of me? Shame on you both! You know that I have been saying all along that I have no interest in installing beta point updates, right? Isn't that what I have been preaching to others here? You know that I am trying to remain firm about this, right? So why are you trying to ruin my reputation? Why, why,why? Are you trying to weaken my resolve?
What I may do -- just out of curiosity to see how it goes -- is use my current external USB 16A323 installer partition as a destination for a full install of Sierra -- assuming that the 16A323 installer will even let me recognize it from my internal hard drive -- and then see if I can apply the 10.12.1 beta there. I don't dare let the 10.12.1 installer install on my internal hard drive on this machine. Too risky. That is why I just moved the installer packages from /Library/Updates to another location on my hard drive.
BTW, if I wanted to do a manual install, would I need to run all three of those packages in a certain order, or is there one in particular which I should double-click, and then it will automatically run the other two?
Yeah, go ahead and PM me the developer notes for 10.12.1 if there is anything of real interest in them for a non-developer like me.
Thanks.
PS: Looks like we were typing out our messages at the same time, but you beat me to the punch.
Well, I see that you have "officially" become foxlet's PR agent.
I'm probably just going to abandon my software update patch tool project, since this is a much better, more reliable, and more streamlined solution. I'll probably throw together a GUI tool that will allow users to easily apply @foxlet's catalog URL on their systems.
Oh gosh . . . Okay . . . I quickly figured it out when I went back and read what you and foxlet had posted earlier.
I now realize that I don't even need those two catalog files that were downloaded when I clicked on those two links . . . although I am wondering what would happen if I were to place them, say, in my Home folder, and then use a local path in that first command string, instead of his web server URL.
Even if it were to work, there is really no advantage in it, I suppose, being as the App Store would still need to connect to his server in order to actually download the install packages themselves.
I must say though, that after seeing how this works, I can see why you have been raving about it so much. It is obviously a lot easier than dosdude1's patch tools method, if one doesn't mind typing a few commands in the Terminal to get the ball rolling. I mean, oh gosh . . . no patches required? And your unsupported machine recognized? What more can we ask for?
So if I understand this correctly, the way that this works is that after changing Apple's default public catalog to the catalog on foxlet's web server, Software Update is automatically set to check his server for updates, instead of Apple's servers, and if there are updates, to enter them in the App Store app. The updates are then downloaded from his server as well.
So can you verify that this is in fact an automated process, and that those three command strings only need to be entered into the Terminal one time in order to get things started?
I mentioned earlier that I would need some compelling reason to switch from dosdude1's method to foxlet's method. Well, I would say that this ease of use -- without the necessity of us personally applying patches and post installs is a pretty compelling reason to switch.
I bet you just loved reading that last line.
In looking at the two methods, I suppose what it really comes down to are two primary issues:
1. Trusting dosdude1 and foxlet to be honest gentlemen who will do nothing to compromise our machines by injecting malicious or dangerous code into their patches.
2. Trusting and hoping that dosdude1 will not tire of updating his patches, and trusting and hoping that foxlet will not tire of updating his catalogs, and keeping the latest builds on his web server.
Yes, I am really thinking this issue through.
So now the big, BIG question: Why did you two -- pkouame and foxlet -- have to dangle this new carrot in front of me? Shame on you both! You know that I have been saying all along that I have no interest in installing beta point updates, right? Isn't that what I have been preaching to others here? You know that I am trying to remain firm about this, right? So why are you trying to ruin my reputation? Why, why,why? Are you trying to weaken my resolve?
What I may do -- just out of curiosity to see how it goes -- is use my current external USB 16A323 installer partition as a destination for a full install of Sierra -- assuming that the 16A323 installer will even let me recognize it from my internal hard drive -- and then see if I can apply the 10.12.1 beta there. I don't dare let the 10.12.1 installer install on my internal hard drive on this machine. Too risky. That is why I just moved the installer packages from /Library/Updates to another location on my hard drive.
BTW, if I wanted to do a manual install, would I need to run all three of those packages in a certain order, or is there one in particular which I should double-click, and then it will automatically run the other two?
Yeah, go ahead and PM me the developer notes for 10.12.1 if there is anything of real interest in them for a non-developer like me.
Thanks.
PS: Looks like we were typing out our messages at the same time, but you beat me to the punch.
Well, I see that you have "officially" become foxlet's PR agent.
It is exciting. That's why I deem it worthy of attention., but the first I did a while back was read the actual catalog entries and compare them against official ones etc...You'll find that official Apple content delivery networks are used. (open the catalogs in a any text editor or browser)