X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 30 Jan 2019 14:49:54 +0100 (CET)
X-X-Sender: igor2 AT igor2priv
To: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Refdes bug or Master Attribute Document on the Wiki
 needs update.
In-Reply-To: <alpine.DEB.2.20.1901301419360.1543@nimbus>
Message-ID: <alpine.DEB.2.00.1901301448260.21900@igor2priv>
References: <9ed059c0-f3c5-1482-169b-f8f1119f3208 AT fastmail DOT com> <alpine DOT DEB DOT 2 DOT 20 DOT 1901301419360 DOT 1543 AT nimbus>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
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



On Wed, 30 Jan 2019, Roland Lutz wrote:

> In what kind of situation would you want to merge components with individual
> refdes' into a single package?  Or, spelled differently, why would you want to
> assign individual refdes' to a package's components?

In some systems this is how you do slotting. Each slot is <refdes>[a..z]. 
I haven't used such system, but I have seen this convention on schematics 
produced with those systems.