[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Notes from last night's Free Dog meeting (11.3.2005) . . . .

To: geda-user@xxxxxxxx
Subject: Re: gEDA-user: Notes from last night's Free Dog meeting (11.3.2005) . . . .
From: Jakub Piotr CÅapa <jpc@xxxxxxxxxxxxx>
Date: Tue, 08 Nov 2005 19:10:21 +0100
Delivered-to: archiver@seul.org
Delivered-to: geda-user-outgoing@seul.org
Delivered-to: geda-user@seul.org
Delivery-date: Tue, 08 Nov 2005 13:11:09 -0500
In-reply-to: <20051104165840.A2ED52AA07@earl-grey.cloud9.net>
References: <20051104165840.A2ED52AA07@earl-grey.cloud9.net>
Reply-to: geda-user@xxxxxxxx
Sender: owner-geda-user@xxxxxxxx
User-agent: Thunderbird 1.5 (X11/20051025)

Stuart Brorson wrote:

Always install gEDA into its own
directory!  Then, when upgrade time comes, just blow away the
directory and start afresh.  Also, make sure that the env variables
are set correctly!

Note that this is good advice for any application suite on unix, not
just gEDA.

That's what /usr/local and /opt were thought for so I think that's a good idea. Of course one should still allow for easy packaging because packages from distro vendor are better for 90% of the tasks than any compiling from source or binary tarballs.

--
Regards,
Jakub Piotr CÅapa

Follow-Ups:
- Re: gEDA-user: Notes from last night's Free Dog meeting (11.3.2005)
  - From: Stuart Brorson

References:
- gEDA-user: Notes from last night's Free Dog meeting (11.3.2005) . . . .
  - From: Stuart Brorson

Prev by Author: Re: gEDA-user: which linux?
Next by Author: Re: gEDA-user: specifying data output in gnucap
Previous by thread: Re: gEDA-user: Notes from last night's Free Dog meeting (11.3.2005) . . . .
Next by thread: Re: gEDA-user: Notes from last night's Free Dog meeting (11.3.2005)
Index(es):
- Author
- Thread