Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Feb 2012 14:51:36 -0900
From:      Royce Williams <royce.williams@gmail.com>
To:        Doug Barton <dougb@freebsd.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: portupgrade -> portmaster Rosetta Stone?
Message-ID:  <CA%2BE3k93cysmUUBEvd50VcmrmVR8AQyDWd=HhKMHhbrON-X_h=Q@mail.gmail.com>
In-Reply-To: <4F4AC302.6030105@FreeBSD.org>
References:  <CA%2BE3k93doEmK7YpiZLgBCB5WUmOeCCLLLQBak_-Nx8sGqiafhQ@mail.gmail.com> <4F49354C.1050803@infracaninophile.co.uk> <4F495B6E.1090604@FreeBSD.org> <CA%2BE3k93uWzvcRKTc_3WJCj6ZzdT3AXsRgfGYTd9Hc7EzTkjUmw@mail.gmail.com> <4F4AC302.6030105@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 26, 2012 at 2:40 PM, Doug Barton <dougb@freebsd.org> wrote:
> On 02/25/2012 16:33, Royce Williams wrote:
>> I really did mean that I was looking for a Rosetta Stone
>
> Yes, I know what a Rosetta Stone is, so I understood what you were
> asking for.

Apologies - I didn't mean to imply otherwise!

> But there are (at least) 3 problems with that approach:
>
> 1. I never used portupgrade, so I couldn't answer those questions anyway.

Understood.  For me, I will have to answer them, and I'd like to
"cache" the results so that others can follow.  Perhaps it will make
migration easier for others like myself.

> 2. By trying to "cheat" the learning process you miss out on the ability
> to challenge your own thinking about why and how you do things. And finally,

My intent wasn't so much to cheat as to supplement.  After ingesting
the entire man page, I suspect that I'll need a quick reference for
some time.

> 3. They are different tools, with different approaches, and not
> everything you did with portupgrade can (or often should) translate
> directly to something you can or should do with portmaster.

Populating that field in the Rosetta Stone table with "n/a", or a
short explanation of the can/should info should help people quickly
track down those gaps and gotchas.  In fact, that's where the value of
such a reference could really shine, IMO.

> Don't bother with the output of --help now, it is there only for a quick
> reference once you've learned something about how the program works.
> There is no substitute for *actually reading the man page.*

Understood, and agreed wholeheartedly.

> If, instead of trying to find ways not to read it, you had spent the 10
> or 20 minutes it should take you to *actually* read it, you'd be well on
> you way by now. :)

Just trying to leverage my work so that others can benefit.  I hope to
find a balance somewhere between a non-man-page-readin' crutch and a
useful cross-reference ... hopefully more toward the latter.

Maybe it's best if I just pipe down now and actually start, and
solicit feedback once there's something to feed back about.  Perhaps,
once I start, I'll find that there's not a lot of value in it.  But
for those of us not fluent in both, there's only one way to find out!
:-)

Royce



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BE3k93cysmUUBEvd50VcmrmVR8AQyDWd=HhKMHhbrON-X_h=Q>