Twas said by " Michael Nottebrock" and my ignorance encourages me to join
the dialogue
> On Tuesday, 10. May 2005 23:42, [EMAIL PROTECTED] wrote:
>
>> I would argue that Readme files can play a role towards dispell7ng the
>> difficulties which arise from a condition which is to be anticipated.
>
> Well, to be perfectly honest I have no idea what such a readme would
> contain
> but gratuitous repetitions of information readily available elsewhere.

I think this could be usefully discussed within a context that sees such a
proposal as worthy of positive consideration.

Certainly I would not support the inclusion of any materials which would
be disparaged by newcomers as gratuitous. It may possibly include (I
think) procedures for Installation, configuration and maintainance and the
default file structure for an installed port. The inclusion of  list and
an overview of optional tools might also be valuable.

Even if the information appears elsewhere a file which is immediately
accessible with the port, at the time of installation,could be invaluable
as both a guide and a reassurance to those who are unsure of what to do,
when and in what order.

/*....make could be used to provide an option to display the Readme before
installation begins -- in that way users could be asked to confirm they
have completed any stages referred to in a checklist -- there could be an
option not to display for experienced hands .....*/

The inclusion of a users introduction intended to provide an overview of
the package and its features might have addiional value but that would
have to be a much more long term project.

Some of that data could be by reference to a web site.

(However I am cautious about that because not all systems may be installed
withdirect access to the internet - a circumstance that is easily
forgotten about AND MORE IMPORTANTLY web addresses change and one would
not want the information to be out of date!)

It might include information which old hands would not regard as necessary
to those who already know!



>
> Note that the 'make install' versus 'make && make install' procedure I
> advised
> you about is *not* to blame for any of the actual problems you've been
> experiencing (I've mentioned in my previous email the possible fallout
> from
> that).

I tend to agree with you but although I now know what caused some of the
problems most of the others were resolved by cleaning out and rebuilding
some libraries.

Regards

David



>


David Southwell              Ham call sign M0TAU
   ****Remove  nospamme_ from reply to ******                             
                       40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V
Taurus. Currently in San Diego, CA. Sailing May bound for Europe via
Panama Canal.
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd

Reply via email to