X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] Config in unstable
Date: Tue, 27 Nov 2012 22:19:08 +0100
Lines: 58
Message-ID: <k93aob$6k7$1@ger.gmane.org>
References: <871ufigr8z DOT fsf AT dome DOT home> <87sj7y3umb DOT fsf AT harrington DOT peter-b DOT co DOT uk> <20121127044128 DOT 112d07ea AT akka> <877gp748ft DOT fsf AT harrington DOT peter-b DOT co DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-183-3-19.net-htp.de
User-Agent: KNode/4.4.11
Reply-To: geda-user AT delorie DOT com

Peter TB Brett wrote:

> Yes. Unfortunately there is not currently any better way to alert
> users that their rc files are out-of-date.

How about this:
On start-up check for the file $HOME/.gEDA/version . If does not 
exist, then show a large and friendly message that explains the 
potential breakage and what to do about it. On close touch the version 
file. 


> Flailing horribly and printing
> error messages is more efficient at this stage than trying to guess
> what the user wants.

At my day-job I try to establish geda in a windows dominated 
environment. Seemingly spontaeous failure would contribute to 
predudices.


> I attempted to write some code that tried to DTRT
> with the legacy "paper-size" function but it was both fragile and
> really confusing.

If doing the right thing is not feasable, then a fair and explicit 
warning would be second best.


> 1.9.0 is going to be a horribly "neither one thing nor the other"
> release.  There will be lots of new features and bug fixes in there,
> but *all* geda-gaf configuration is going to be in flux throughout
> the 1.9.x release series.

For the record: I welcome changes for the better, even if they break 
old habits. This is much better in the long run than the almost freeze 
of the gschem UI we had for the last years.


> 6) "Use the Source, Luke!" and submit a patch.

Friendly reminder: Any reaction from the devs to a submitted patch is 
encouraging. Even a "won't fix" is better than plain nothing.

 
> N.b. "post a passive-aggressive e-mail to the mailing list" is not
> one of the recommended steps for promptly resolving your issue.

I feel like this is targeted at me. Be assured, that my mails are not 
meant to be aggressive in any way. When I describe problems, it is to 
be informative. If it did not sound like it, this may be a consequence 
of english being a foreign language to me.

Looking forward to (breaking) changes,

---<)kaimartin(>---
-- 
Kai-Martin Knaak