X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Wed, 9 Dec 2015 20:28:45 -0500 Message-Id: <201512100128.tBA1SjW8000759@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: <20151210011215.14229.qmail@stuge.se> (geda-user@delorie.com) Subject: Re: [geda-user] gsch2pcb after refdes-renum? (If implemented syncronization detail) References: <20151208205451 DOT bb2478f8722e1a885822689d AT gmail DOT com> <201512082019 DOT tB8KJOlP030874 AT envy DOT delorie DOT com> <20151208222204 DOT 6566ebed300ca2683dd71bc8 AT gmail DOT com> <201512082139 DOT tB8LdLuL005789 AT envy DOT delorie DOT com> <20151208230637 DOT b8eb6c22230d5a3b977c3ca1 AT gmail DOT com> <201512082229 DOT tB8MTJBj010408 AT envy DOT delorie DOT com> <555EDA31-984C-4978-AE21-F74907CDC993 AT noqsi DOT com> <20151209220625 DOT ba29467498daecf1bf7b2244 AT gmail DOT com> <201512092109 DOT tB9L9p8o022465 AT envy DOT delorie DOT com> <20151210011215 DOT 14229 DOT qmail AT stuge DOT se> 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 > Is there still a problem if the cyclic U1->U2->U3->U1 rename is > guaranteed to be atomic? You still have two problems: First, if you accidentally run the script twice, you end up with the wrong refdeses. Second, you need to remember the refdes the part had *the last time you sync'd*. If the layout[*] still had U14 because you last sync'd yesterday and you've renamed it five times today, you're out of luck. This whole identity-across-projects problem is hard, especially when you consider how many ways "refdes as identity" is abused in gnetlist (slots, mcus, heirarchy, whatever). Which makes it a research-level problem, which is why I asked if anyone was working on it. [*] or whatever else jpd is exporting to