On Wed, 19 Jan 2005, Horsley Tom wrote:
> I've been watching this thread from the peanut gallery out here, and
> have some general reactions to various points that have been made:
>
> I'm sure fixing the build procedures is a monumental pain in the
> patoot, but it also seems like the right thing
Horsley Tom wrote:
> I've been watching this thread from the peanut gallery out here, and have
> some general reactions
> to various points that have been made:
I love graphic metaphors.
> I'm sure fixing the build procedures is a monumental pain in the patoot, but
> it also seems
> like the ri
> I can even imagine the day perl.org might have a dynamic tarball
> builder that would
package up a custom "sdk" for you to download on
> the fly with your very own collection
of modules custom installed
> and all you need to do is one big make, make test, make install.
You build it, we'll fig
I've been watching this thread from the peanut gallery out here, and have some
general reactions
to various points that have been made:
I'm sure fixing the build procedures is a monumental pain in the patoot, but it
also seems
like the right thing to do for various reasons:
1. What kind of im
On Wed, Jan 19, 2005 at 09:20:02AM +, Nick Ing-Simmons wrote:
> Jos I. Boumans <[EMAIL PROTECTED]> writes:
> >> It is certainly possible to write files without the FileHandle module.
> >> It may well be more convenient to do whatever it is you are doing
> >> with various modules,
> >> but it
On Jan 19, 2005, at 3:55 PM, Andrew Dougherty wrote:
On Wed, 19 Jan 2005, Jos I. Boumans wrote:
Although i'm sure this is all correct, it actually doesn't address the
issue i raised, just a symptom we observe. The real problem is, as
stated in the original post:
What do we do when we want t
On Wed, 19 Jan 2005, Jos I. Boumans wrote:
> Although i'm sure this is all correct, it actually doesn't address the
> issue i raised, just a symptom we observe. The real problem is, as
> stated in the original post:
>
> What do we do when we want to integrate modules into the core that
>
Randy W. Sims <[EMAIL PROTECTED]> writes:
>Jos I. Boumans wrote:
>> So, in order of preference, i like these options:
>> 2) build simple ones first, then complex ones; easiest for cpanplus :)
>> 5) execute Makefile.PLs in lib/CPANPLUS; requires configure changes
>> 3) add a 'make config
Jos I. Boumans <[EMAIL PROTECTED]> writes:
>
> What do we do when we want to integrate modules into the core that
> require core XS modules to build themselves?
Sigh, and reject the module as non-integratable.
This ties in with the periodic "different sized standard perls" discussions
According to Jos I. Boumans:
> Although i'm sure this is all correct, it actually doesn't address the
> issue i raised, just a symptom we observe. The real problem is, as
> stated in the original post:
>
> What do we do when we want to integrate modules into the core that
> require c
On Jan 19, 2005, at 10:44 AM, Randy W. Sims wrote:
Jos I. Boumans wrote:
So, in order of preference, i like these options:
2) build simple ones first, then complex ones; easiest for
cpanplus :)
5) execute Makefile.PLs in lib/CPANPLUS; requires configure
changes
3) add a 'make config';
Jos I. Boumans wrote:
> Although i'm sure this is all correct, it actually doesn't address the
> issue i raised, just a symptom we observe. The real problem is, as
> stated in the original post:
>
> What do we do when we want to integrate modules into the core that
> require core XS
Jos I. Boumans wrote:
So, in order of preference, i like these options:
2) build simple ones first, then complex ones; easiest for cpanplus :)
5) execute Makefile.PLs in lib/CPANPLUS; requires configure changes
3) add a 'make config'; bit more tedious, but we get both tests +
config
On Jan 19, 2005, at 10:20 AM, Nick Ing-Simmons wrote:
Jos I. Boumans <[EMAIL PROTECTED]> writes:
It is certainly possible to write files without the FileHandle
module.
It may well be more convenient to do whatever it is you are doing
with various modules,
but it's not obviously essential to have
Jos I. Boumans <[EMAIL PROTECTED]> writes:
>> It is certainly possible to write files without the FileHandle module.
>> It may well be more convenient to do whatever it is you are doing
>> with various modules,
>> but it's not obviously essential to have those modules.
>It's almost never 'essent
Jos I. Boumans <[EMAIL PROTECTED]> writes:
>
>I've started with putting CPANPLUS into ext/ as we require it's
>Makefile.PL to be run (this is not easily changed, nor should it be
>needed). But CPANPLUS loads other modules, including FileHandle, which
>uses IO::Handle, which uses IO, which is an
On Jan 18, 2005, at 9:28 PM, Andy Dougherty wrote:
On Tue, 18 Jan 2005, Jos I. Boumans wrote:
On Jan 18, 2005, at 7:20 PM, Andy Dougherty wrote:
All this desribes the bigger problem of: What do we do when we want
to
integrate module into the core that require core XS modules to build
themselves?
I
On Tue, 18 Jan 2005, Jos I. Boumans wrote:
>
> On Jan 18, 2005, at 7:20 PM, Andy Dougherty wrote:
> >> All this desribes the bigger problem of: What do we do when we want to
> >> integrate module into the core that require core XS modules to build
> >> themselves?
> >
> > I've never run into this
Andy Dougherty wrote:
> On Tue, 18 Jan 2005, Chip Salzenberg wrote:
>
> > According to Jos I. Boumans:
> > > One of the solutions suggested was to use miniperl to build perl first
> > > and use perl to build the extensions (rather than miniperl)...
> >
> > That'd be an interesting trick, seeing as
On Tue, 18 Jan 2005, Chip Salzenberg wrote:
> According to Jos I. Boumans:
> > One of the solutions suggested was to use miniperl to build perl first
> > and use perl to build the extensions (rather than miniperl)...
>
> That'd be an interesting trick, seeing as how perl is miniperl plus
> static
According to Jos I. Boumans:
> One of the solutions suggested was to use miniperl to build perl first
> and use perl to build the extensions (rather than miniperl)...
That'd be an interesting trick, seeing as how perl is miniperl plus
static extensions. Did you perchance mean "the dynamic extens
On Jan 18, 2005, at 7:20 PM, Andy Dougherty wrote:
All this desribes the bigger problem of: What do we do when we want to
integrate module into the core that require core XS modules to build
themselves?
I've never run into this problem, so I can only state the obvious.
How essential, really, is Fil
On Tue, 18 Jan 2005, Jos I. Boumans wrote:
> in the attempt to generate a patch-set that would include CPANPLUS (and
> some abstracted out modules) to the core, i've run into the following
> problem:
>
> Making CPANPLUS (nonxs)
> Can't load module IO, dynamic loading not available i
Hi,
in the attempt to generate a patch-set that would include CPANPLUS (and
some abstracted out modules) to the core, i've run into the following
problem:
Making CPANPLUS (nonxs)
Can't load module IO, dynamic loading not available in this perl.
(You may need to build a ne
24 matches
Mail list logo
