X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type; bh=T5GOBNHRb8caG+718iUYOgXi5IHLVxndRuPlSIIcNDY=; b=QJcXHZo0ZkGZ0imQQDndVpMIpQb6H3WSiGo7nav/7/VcCKNYLqtx6Dfsq6YtXwq9t1 7+wFO4jB9nS/eUmkqA2D6xR8iFQzbezfg7xY7aHZDUx8U9c+eXohB9yVG6FHhKFoD7m5 PdKjpdGN6oSqBADRGTXgXsJCFi+3sMZ+4+e+OywxwhWQIpiOPKCH8Crzz8p1IRm4ipkh mZCV50LItPiG3ZPFhrhOVns2iGWdWYQhpbeuD6PFJg9hKxdu5YlC3quhIyjOriwf4V17 wDCUcbVhbnxGWyxmo8aP1WNyo9i5dd9ka8BKv2D75UYbIFMC4uanIbRxWshoIO/PzrF8 LvkA== X-Received: by 10.52.17.70 with SMTP id m6mr90350535vdd.92.1358199806353; Mon, 14 Jan 2013 13:43:26 -0800 (PST) From: Ben Gamari To: Enoch , geda-user AT delorie DOT com Subject: Re: [geda-user] geda-skeleton-project: Lowering the cost of a starting a gEDA project In-Reply-To: <877gnfijh1.fsf@dome.home> References: <87wqvhd4tw DOT fsf AT gmail DOT com> <87boctuh9a DOT fsf AT dome DOT home> <874nijvini DOT fsf AT gmail DOT com> <877gnfijh1 DOT fsf AT dome DOT home> User-Agent: Notmuch/0.14+240~g0ab5e9f (http://notmuchmail.org) Emacs/23.4.1 (x86_64-pc-linux-gnu) Date: Mon, 14 Jan 2013 16:43:24 -0500 Message-ID: <87y5fvmoeb.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Enoch writes: > Ben Gamari > writes: > >> Enoch writes: >> >>> A good starting point. >>> >>> 1. Let the skeleton-geda-project replicate itself rather than rename. >>> >> I was on the fence about how to approach this. Sleeping over it, I think >> you are right. Cloning a new repository is a bit nicer than renaming the >> original. > > I am sure many would like to "git pull" your project often without it > disappearing after each "delivery" :-) > Have a look at how things are done now. The init script now clones the directory it sits within and modifies the newly created project directory. >> Further concrete suggestions for default configuration options would be >> quite welcome. > > For example, I have in gschemrc the following: > > (load-from-path "auto-uref.scm") ; load the autonumbering script > (add-hook! add-component-hook auto-uref) ; autonumber when adding a component > (add-hook! copy-component-hook auto-uref) ; autonumber when copying a component > > I find this feature useful when doing design changes. > Ahhh, I see. An interesting point. I personally did not know about the autonumbering script. I use gschem more or less unmodified but only for lack of knowledge of snippets like this. > Such scheme snippets though should be introduced as options. > Yes, I'm not sure how much configuration I want to impose upon unsuspecting users. That being said, it's possible that enabling autonumbering would be a reasonable default. Cheers, - Ben