RPM: packaging the perl5/parrot libraries

2007-09-20 Thread David Fetter
Folks, Please find attached a .spec file I've slightly modified from the one that comes with the Parrot 0.4.16 tarball. It doesn't yet include a way to make the Parrot:: libraries for Perl 5. Any ideas how to help it do this? Right now, I can build it on Fedora 7 with: QA_RPA

Re: Parrot Libraries

2004-04-08 Thread Dan Sugalski
At 11:00 PM +0200 4/7/04, Jens Rieks wrote: On Wednesday 07 April 2004 21:57, Dan Sugalski wrote: > At 8:50 AM +0200 4/7/04, Leopold Toetsch wrote: > >3) we need some scheme to organize lib paths We might want to think about library metadata as well. I'm half-tempted to go with a full-blown d

Re: Parrot Libraries

2004-04-07 Thread Jens Rieks
On Wednesday 07 April 2004 21:57, Dan Sugalski wrote: > At 8:50 AM +0200 4/7/04, Leopold Toetsch wrote: > >We still have two locations for runtime stuff: > >- runtime/parrot/*/ > >- library/ > > Let's move everything to runtime/parrot I can take care of it when I have checkin access. > >1) We shou

Re: Parrot Libraries

2004-04-07 Thread Dan Sugalski
At 8:50 AM +0200 4/7/04, Leopold Toetsch wrote: We still have two locations for runtime stuff: - runtime/parrot/*/ - library/ Let's move everything to runtime/parrot 1) We should probably decide to use just one for simplicity. 2) Library search paths and appropriate helper functions inside Parrot

Re: Parrot Libraries

2004-04-07 Thread Leopold Toetsch
Jens Rieks <[EMAIL PROTECTED]> wrote: > Hi, > On Wednesday 07 April 2004 08:50, Leopold Toetsch wrote: >> - runtime/parrot/*/ > This directory does only include generated files, doesn't it? Almost. We have in CVS: - runtime/parrot/include/DWIM.imc - runtime/parrot/include/Getopt_Long.imc - runti

Re: Parrot Libraries

2004-04-07 Thread Jens Rieks
Hi, On Wednesday 07 April 2004 08:50, Leopold Toetsch wrote: > - runtime/parrot/*/ This directory does only include generated files, doesn't it? > - library/ Maybe move it to runtime/library? We can also create a runtime/t/ (or t/runtime) where the library tests can go to. > 1) We should probabl

Parrot Libraries

2004-04-06 Thread Leopold Toetsch
We still have two locations for runtime stuff: - runtime/parrot/*/ - library/ 1) We should probably decide to use just one for simplicity. 2) Library search paths and appropriate helper functions inside Parrot are still needed. 3) we need some scheme to organize lib paths 4) Library testing is nee