On Sun, 2008-07-27 at 12:10 -0700, Will Coleda via RT wrote:
> On Sun, Jul 27, 2008 at 1:08 PM, via RT Geoffrey Broadwell
> <[EMAIL PROTECTED]> wrote:
> > # New Ticket Created by  Geoffrey Broadwell
> > # Please include the string:  [perl #57344]
> > # in the subject line of all future correspondence about this issue.
> > # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=57344 >
> >
> >
> > In the source repository, the 'parrot' in runtime/parrot/foo is
> > pointless.  It's a singleton directory, and it's redundant.
> >
> > It also means that when we install, we either end up with silly
> > directories like /usr/lib/parrot/runtime/parrot/foo/, or we have to
> > clutter the .include and load_bytecode code with checks in both
> > <prefix>/runtime/parrot/foo/ *AND* <prefix>/runtime/foo/.
> >
> > The solution to this is to fix the source tree -- move the children of
> > runtime/parrot/ up one level, and get rid of the 'parrot' directory.
> >
> > In summary, there are three things that can budge, depending on how you
> > view this problem: cleanliness, performance, and the source tree.  I
> > vote for fixing the source tree.
> 
> What about the runtime for things that are not core parrot, for
> example, the runtimes of the various languages? Tcl, for example, has
> a runtime PBC, op library, and some dynpmcs.[1]
> 
> (Which don't go into a separate place under runtime at the moment, but
> arguably could.)

I thought of that.  rurban (I think) said on IRC that the language
dynpmcs go in .../dynext already, and other libraries either do, or
could, go under .../library.

Now, if we decide to standardize on moving all language runtimes to
siblings of runtime/parrot, I'd be fine with leaving it.  But my
understanding is that over time, the languages will migrate out of the
repo altogether.  Of course, this hasn't happened yet, because every
time we change fundamentals in Parrot, we need to fix all the languages.
Having Kea-CL out of tree has already shown the problems there.  There's
also nothing that says that even when moved out of tree eventually, we
can't make them all use the same directory structure under runtime/ ....

So: either we decide to actually move things from the languages to
parallel runtime/parrot/, or we should remove the singleton /parrot/
directory from the middle of the path.


-'f


Reply via email to