From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,c6567772e9f3871d,start
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!q13g2000vby.googlegroups.com!not-for-mail
From: Greg Moncreaff <moncreg@gmail.com>
Newsgroups: comp.lang.ada
Subject: organizing deep source trees with child packages
Date: Wed, 12 Oct 2011 16:38:27 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: 
 <21c9e6bb-f4f7-4a00-bde7-68f2c1a42d01@q13g2000vby.googlegroups.com>
NNTP-Posting-Host: 199.46.198.231
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1318464207 22860 127.0.0.1 (13 Oct 2011 00:03:27
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 13 Oct 2011 00:03:27 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: q13g2000vby.googlegroups.com; posting-host=199.46.198.231;
 posting-account=95T5lgoAAADbcAro2csVwCIG3o1qfV_4
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: ASELNKCHRU
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.1;
 rv:7.0.1) Gecko/20100101 Firefox/7.0.1,gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:21401
Date: 2011-10-12T16:38:27-07:00
List-Id: <comp.lang.ada>

Have a 3 level (so far) tree of packages

foo/bar/narf

foo/foo.ads
foo/bar/foo-bar.ads
foo/bar/narf/foo-bar-narf.ads
foo/bar/narf/foo-bar-narf-able.ads
foo/bar/narf/foo-bar-narf-able.adb
foo/bar/narf/foo-bar-narf-baker.ads
foo/bar/narf/foo-bar-narf-baker.adb
foo/bar/narf/foo-bar-narf-charlie.ads
foo/bar/narf/foo-bar-narf-charlie.adb

as you can see, the full paths of the items are visually silly, and
somewhat painful if the tree needs refactoring

is there some way of renaming the parent package along the way to
tighten up the names?,
without having to have naming blocks in the .gpr files?

e.g. I would like something like

foo/bar/narf/narf-able.ads
foo/bar/narf/narf-able.adb
foo/bar/narf/narf-baker.ads
foo/bar/narf/narf-baker.adb
foo/bar/narf/narf-charlie.ads
foo/bar/narf/narf-charlie.adb

if by some magic

foo/bar/narf/narf.ads could define

package Narf renames Foo.Bar.Narf

and then

foo/bar/narf/narf.ads could be

package Narf.Able is ...


or is this hopeless desire and an exercise with no value?