X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=94ebn51BXJBVUO+pFjn5cSmsn/i+5+Z5Wdsx0L4SIx8=;
	b=kg0YjKpsrvWOwd0snnIaaaNZDSQtVUMpoxiU7jPawWBlKd+u7Sss/niYm4O5ny8SOY
	jAvmMUJhTarVOYVwxzhPKu1d+6mYLev3VRk4gCdBAWOH7SQ+yn/ZN4TN9LdIxXIGHaah
	xCM5ISKjNatL2i+BVmSfSMwiJUeNpngcb28pnqAH5tO8wHreWPvB1+uY1+/xNk0dWfdK
	VwIEtin0DQk7VZVJlMOOObIiTAoTmL+/g2O2C9SC4fn5w0ggzbP2NgY0U7vX+gUKfBny
	j2xBzFqvthVzS5WswAbZtpdLL7f7VrQPnPVuZYfEwCTPmgPHCaltZcqGauLFf5Dr7yiU
	7WtQ==
MIME-Version:	1.0
X-Received:	by 10.194.109.97 with SMTP id hr1mr19396281wjb.38.1442162975153;
	Sun, 13 Sep 2015 09:49:35 -0700 (PDT)
In-Reply-To:	<B4456298-B5D7-46D0-A569-D9FDA964B923@noqsi.com>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1509111150410 DOT 2482 AT lichen>
	<B94E2C24-8B63-46FC-A551-9E4B14B817C9 AT noqsi DOT com>
	<201509111624 DOT t8BGOPYV000685 AT envy DOT delorie DOT com>
	<F24E14C9-8427-4688-A27A-1EBE0F669995 AT noqsi DOT com>
	<201509111732 DOT t8BHWnF7005271 AT envy DOT delorie DOT com>
	<960028A6-F16B-4276-B838-E9F0D2959A6F AT noqsi DOT com>
	<55F32375 DOT 2020505 AT ecosensory DOT com>
	<FC9C2933-89CE-44FD-A9EE-CA2721405ACE AT noqsi DOT com>
	<201509111941 DOT t8BJfqWl010427 AT envy DOT delorie DOT com>
	<D3D5A923-FAF9-4665-A0DB-A8D6A8BEA5A3 AT noqsi DOT com>
	<CA+uY=MS5ZOTHXDe9taav+0tCiZOqhtAJU2KO-xyRA3SrQVvLNw AT mail DOT gmail DOT com>
	<201509112020 DOT t8BKKBgI012564 AT envy DOT delorie DOT com>
	<E872F1BC-8FA7-449E-BA6D-5841AC79A465 AT noqsi DOT com>
	<201509112058 DOT t8BKwF3b013774 AT envy DOT delorie DOT com>
	<6341DF3E-543D-4E36-9B01-6B5B950208C4 AT noqsi DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1509121245420 DOT 3577 AT lichen>
	<9D45499A-BC67-4B2F-A285-34C49ECC20B0 AT noqsi DOT com>
	<55F451F4 DOT 8000100 AT ecosensory DOT com>
	<AD39C282-9689-46B8-8957-4958D5532B8B AT noqsi DOT com>
	<55F47539 DOT 9090006 AT ecosensory DOT com>
	<BE55E73E-3459-4421-8067-DFDAEEFE2624 AT noqsi DOT com>
	<CAC4O8c8_JSB4ZDNFDdhX2Nnk8+q8ejYohgC+u2TBOyyErtw4tg AT mail DOT gmail DOT com>
	<B4456298-B5D7-46D0-A569-D9FDA964B923 AT noqsi DOT com>
Date:	Sun, 13 Sep 2015 08:49:34 -0800
Message-ID:	<CAC4O8c_xtu+Q0HbfW6EDJ06UNf-ChqM3+HeMzfonDSWkaNibUA@mail.gmail.com>
Subject:	Re: [geda-user] About reinventing the wheel, and how to avoid it
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t8DGndiO018950
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

>>>> It great to separate things into
>>>> modules but there's no point in not storing and distributing them
>>>> together with the core distribution.
>>>
>>> I think many would find a 50 MB distribution a bit much.
>>
>> By modern standards, this is minute.
>
> Oh, anybody can *store* it. But comprehend it?

Putting it somewhere else doesn't make it more comprehensible, just
harder to find
and use.

>>> Simply distributing a mixed bag of stuff with the core will not relieve confusion.
>>
>> Modules aren't just a mixed bag of stuff, they're pieces designed to work with
>> the core.  It's helpful if people know they exist and can try them easily.
>>
>> Gedasymbols is arguably a lot more mixed since the symbols are created in
>> different ways, but if they had some sort of common interface for
>> build/search etc.
>> I think it would be worth adding them also, since the lack of them is
>> another big
>> weakness of gEDA.
>>
>>> I also see the success of the core/addon approach in other >projects.
>>
>> They are much bigger projects, with established ways of finding the modules.
>> gEDA doesn't have any such way.
>
> We need a way.

Good luck creating one.

>> It's easier to just distribute them with
>> the core than make one and expect it to be adopted.
>
> I don’t think that’s an answer. Successful projects I’m aware of don’t do it that way.

I don't say it's the best possible answer, but it would be better than
the present situation and might actually get done.

- Raw text -