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=20161025;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=3ssWK3AOSNDxDzBdz5nkvZfwGAbnaA44vMpc1k0ztUM=;
        b=HaYcDvQyjZWUebThrQfsbNl41C67l6TJytTznpCPfMBFFaLjRcZ6qKzddcOKmGMLJT
         idJN/q2dnihqrw1sDOQOvTllXSQKzjJ/CJFlDtxARBWvJLNH8VfTwsP6I2F52tY2FuiV
         BUdwW2h9dj1jW3MkkkeGQQC0wUFHayWnjm5H/Xf9mrIZVZ4QzQRv4Rba4rMe+Kd2lmls
         oXp7b4D0vYytfRL+je9v1a9lUiAPfshLfBu986huZqy7PXd009Lm7oUPDLZ23AhDmBrC
         pR6HxstywMduVmjO51FNBHOrgKIeRIIybcXgwTcscPn4PHS+4e1XWDg6Ja0P4WugUaIL
         7eIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=3ssWK3AOSNDxDzBdz5nkvZfwGAbnaA44vMpc1k0ztUM=;
        b=pg37Wm9y8KqRYrokuLqJesNTeWWCFcrVqfcI4ZL5AWFEQ21jtkasEKPBbciF9ipKNM
         5VODVcCB2l+Rh5io54HTjyKGvvVn3PBm+PsTjRvYJtIIKaV9fy4NqkgCyQb3rocCDwbX
         nNMFQNwQZ6E6Ut+1pS4gGukKejQQ5YzY6txxiSEXi/zN6AjeeSr+XEIy7Q/TGo+jsAiH
         4Mi5c39zCnrqMSavz8KQiCMDEXHkU7QFiQ2bcvAiXIamuvVux87FmixUzjpUmrNfeIYa
         Gaq/BtimdYr+v1cPjxSiTIO0QLj7Ehs4/fItVfTc6fHaOUHoQ9WNmKhg159LEvv/pDjB
         RO7A==
X-Gm-Message-State: AKGB3mL+kxiq7+ykKDaywJH1iGTSNSBo6eqx5uZoAVJP4AsNf7FdqYc/
	O0nHbxKYlb4DvL7/iQubJavZqQ==
X-Google-Smtp-Source: ACJfBoumtrXPAj2ET3j4/eWVccdTx8oRrQSKSxS6HudXNBRu/RCJCKNeV+hIraWLRD/NCgzj8PKwJQ==
X-Received: by 10.46.78.26 with SMTP id c26mr14091213ljb.90.1514295902806;
        Tue, 26 Dec 2017 05:45:02 -0800 (PST)
Date: Tue, 26 Dec 2017 14:44:59 +0100
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] why pinnumber in sym pins?
Message-Id: <20171226144459.1b6d5748810806a34d8fbb02@gmail.com>
In-Reply-To: <20171226122009.366BF804CEDE@turkos.aspodata.se>
References: <20171226122009 DOT 366BF804CEDE AT turkos DOT aspodata DOT se>
X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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 Tue, 26 Dec 2017 13:20:09 +0100 (CET)
karl AT aspodata DOT se wrote:

>  Why must one have a pinnumber attribute for each pin i a sym file:
> http://wiki.geda-project.org/geda:master_attributes_list#pinnumber
> 
> Wouldn't it suffice to have pinseq and pinlabel ?
> ... it would be nice if one could map sym -> fp with
> just the "pinlabel" (gschem) -> pin "Name" (pcb). But pcb doesn't seem
> to support that idea.
> 
> Any suggestions or pointers ?

Actually gschem do not care about these attributes. Problem is in gnetlist.

In cschem I think core does not care about attributes but plugins might do, for example to map schematic symbol to footprint pin number. But I am not sure.