Robert Spier <[EMAIL PROTECTED]> wrote:
>> > Anyway, we're more than happy to do this once in a while.. We just
>> > require detailed instructions as to what goes where.
As Dan now seems to agree, that imcc (and other files) should go into
its own subdirectory it would be fine, it we could the mo
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Dan Sugalski wrote:
>
> > On Mon, 8 Sep 2003, Leopold Toetsch wrote:
> >
>
> >> Imcc is still lacking full integration inside Parrot. To accomplish
> >> this, we would need these steps:
>
> >>
> >>- rebuild and commit directory structure $Parrot_Roo
> > Anyway, we're more than happy to do this once in a while.. We just
> > require detailed instructions as to what goes where.
> Dan does (again :) disagree, and wants files in $ROOT - but
I'll let you two hash it out. Your reasons sound logical and sensible
to me. Clogging up the $ROOT is pr
Robert Spier <[EMAIL PROTECTED]> wrote:
> The method described below is generally what we do. Not perfect, but
> better than nothing, or just straight removals.
> Anyway, we're more than happy to do this once in a while.. We just
> require detailed instructions as to what goes where.
I'm for a
The method described below is generally what we do. Not perfect, but
better than nothing, or just straight removals.
Anyway, we're more than happy to do this once in a while.. We just
require detailed instructions as to what goes where.
-R (your friendly cvs monkey) (ook ook)
> An alternative
Dan Sugalski wrote:
On Mon, 8 Sep 2003, Leopold Toetsch wrote:
Imcc is still lacking full integration inside Parrot. To accomplish
this, we would need these steps:
- rebuild and commit directory structure $Parrot_Root/imcc
- move files from languages/imcc to ../imcc [1]
- adapt Makefiles
- inc
On Mon, Sep 08, 2003 at 02:24:41PM +0200, Leopold Toetsch wrote:
> The normal way to move a file is to copy OLD to NEW, and then issue
> the normal CVS commands to remove OLD from the repository, and add NEW
> to it.
>
> $ mv OLD NEW
> $ cvs remove OLD
> $ cvs add NEW
>
On Mon, 8 Sep 2003, Leopold Toetsch wrote:
> Imcc is still lacking full integration inside Parrot. To accomplish
> this, we would need these steps:
>
> - rebuild and commit directory structure $Parrot_Root/imcc
> - move files from languages/imcc to ../imcc [1]
> - adapt Makefiles
> - include imc
Imcc is still lacking full integration inside Parrot. To accomplish
this, we would need these steps:
- rebuild and commit directory structure $Parrot_Root/imcc
- move files from languages/imcc to ../imcc [1]
- adapt Makefiles
- include imcc source files except main.c into libparrot
[1] info cvs
*
