On Wed, Feb 15, 2012 at 10:12:06PM +0000, Stuart Henderson wrote: > On 2012/02/15 13:23, Chris Bennett wrote: > > On Wed, Feb 15, 2012 at 08:58:22AM +0000, Stuart Henderson wrote: > > > On 2012-02-14, Chris Bennett <[email protected]> wrote: > > > >> > For -current: > > > >> > Update your ports tree at the SAME time as you update -current, never > > > >> > before or after. > > > >> > > > > >> > make clean > > > >> > make update > > > >> > make repackage > > > >> > make reinstall > > > >> > > > >> Huh???? this reads like an excerpt of freebsd's handbook or something. > > > >> > > > > > > > > Sorry, I pulled this stuff off of www.openbsd.org. > > > > > > Can you point out where? My grep failed to find it. > > > > > > > http://www.openbsd.org/faq/ports/ports.html > > > > make install > > make clean > > make clean=depends > > make clean=dist > > make clean=flavors > > make uninstall > > make reinstall > > make clean=packages > > make install-all > > This page is giving a set of examples of ways to do different things, > it is not a set of instructions to follow in order. > > > http://www.openbsd.org/faq/ports/guide.html > > make build > > No issues with this page that I can see. > > > http://www.openbsd.org/faq/ports/testing.html > > > > make fetch > > make checksum > > make makesum > > make regress > > This page is a guide for testing ports not a guide for standard > ports building. It isn't telling you to 'make makesum' anywhere. > What it's doing is taking you through individual steps in sequence, > one-by-one, so that it's very clear at which point an error occurs. > > Nowhere tells you to 'update/repackage/reinstall' which is > pointless if you think about what it's actually doing: > build a package, update the installed package to the new one, > create the same package again, uninstall the package and > then reinstall it.... >
I am not saying that my exact wording was right on the money. But what happened to don't type commands unless you fully understand them? Isn't what I said pretty much a clear description of what is happening behind the scenes? I was not suggesting that following the port builders guide was the right approach. Obviously not. Is there some harm in following the steps through individually instead of just typing something like: make happen_things? If I am wrong, then tell me why doing things step by step is improper. When I am trying to teach someone something, I make them carry out each individual step repeatedly until they get clarity. I am stubborn, but I always accept "patches" to my way of doing things. Change is a good thing. I have had to make many changes to my idiotic ways over the years. Chris Bennett
