Dave Mitchell:
> Just to clarify this - so there will be 2 separate tarballs, each with
> their own set of READMEs, config scripts etc. You install one of them first,
> then the second install makes use of the just-installed
> /usr/local/lib/parrot.so or perl6.so for its own build
Yes to READMEs,
Simon Cozens <[EMAIL PROTECTED]> wrote:
> Melvin Smith:
> > I agree with your config/ dir suggestion, but I'm not sure about
> > moving everything else down into perl6/parrot subdirectory,
>
> Me neither. I don't see much point in it.
>
> > 1) Will Perl6 and Parrot distributions be separate?
>
On Fri, Feb 08, 2002 at 01:18:20PM +, Dave Mitchell wrote:
> Simon Cozens wrote:
> > Dave Mitchell:
> > > I'm trying to nip the following in the bud, which is daunting for someone
> > > trying to work out what's what for the first time.
> > >
> > > ls perl-current/
> >
> > I see your point,
Simon Cozens wrote:
> Dave Mitchell:
> > I'm trying to nip the following in the bud, which is daunting for someone
> > trying to work out what's what for the first time.
> >
> > ls perl-current/
>
> I see your point, but I don't think 'ls perl-current/src' is much better. :)
True, but the point
Dave Mitchell:
> I'm trying to nip the following in the bud, which is daunting for someone
> trying to work out what's what for the first time.
>
> ls perl-current/
I see your point, but I don't think 'ls perl-current/src' is much better. :)
If we're going to do anything I think we should separ
Simon Cozens <[EMAIL PROTECTED]> wrote:
> Melvin Smith:
> > I agree with your config/ dir suggestion, but I'm not sure about
> > moving everything else down into perl6/parrot subdirectory,
>
> Me neither. I don't see much point in it.
I'm trying to nip the following in the bud, which is daunting
At 12:16 PM + 2/7/02, Dave Mitchell wrote:
>I've only had one reply to this so far - anyone else want to
>approve or disapprove?
Other folks have waded in, and I'm OK with whatever we end up with.
(I do think the idea of separating stuff into subdirs is a Good Thing)
The one objection I hav
Melvin Smith:
> I agree with your config/ dir suggestion, but I'm not sure about
> moving everything else down into perl6/parrot subdirectory,
Me neither. I don't see much point in it.
> 1) Will Perl6 and Parrot distributions be separate?
Yes.
> 2) Should/would perl6 (lex, parser, code-gen, e
[EMAIL PROTECTED]:
# I've been thinking about the directory structure of Parrot.
# Currently, the top-level dir is a bit of mess, with zillions of
# files of various flavours. It is my contention that apart from
# a few expected files such as README, MANIFEST, Configure.pl etc,
# everything else s
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > Anyway, here's how I suggest files should be moved around to make
> > a more rational directory hierarchy. This will involve quite a bit
> > of hacking of paths in makefiles, scripts etc; but if we're going
> > to do it at all, then the sooner the bett
On Thu, 7 Feb 2002, Dave Mitchell wrote:
> I've only had one reply to this so far - anyone else want to
> approve or disapprove?
Uncluttering things, in general, is probably a pretty good thing.
> Anyway, here's how I suggest files should be moved around to make
> a more rational directory hier
cc:
Subject: Re: Parrot directory
structure
I've only had one reply to this so far - anyone else want to
approve or disapprove?
NB - I'm kind of offering to do the patching of paths required if this
move goes ahead, but obviously I can't do the moving on the CVS server
myself.
Dave.
- Begin Forwarded Message -
Da
I think your suggestions sound pretty good to me.Personally, i'd lean
towards possibility 2, since 1 is doable if you plan for 2, but not
necessarily vice-versa.
Otherwise I think your proposal sounds good. But then again i'm nobody ;)
--Josh
At 23:24 on 02/03/2002 GMT, [EMAIL PROTECTED
14 matches
Mail list logo
