[perl #38124] [TODO] build - header file detection w/o perl5

Will Coleda via RT parrotbug-followup at parrotcode.org
Thu Nov 5 06:01:30 UTC 2009


On Sun Feb 08 09:06:33 2009, kjs wrote:
> On Sat, Feb 7, 2009 at 2:37 PM, Will Coleda <will at coleda.com> wrote:
> 
> > On Fri, Feb 6, 2009 at 9:46 PM, Joshua Hoblitt
> <jhoblitt at ifa.hawaii.edu>
> > wrote:
> > > On Fri, Feb 06, 2009 at 06:44:47PM -0800, James Keenan via RT
> wrote:
> > >> On Sun Jan 01 19:09:51 2006, jhoblitt at ifa.hawaii.edu wrote:
> > >> > auto::headers uses the Config module to detect installed header
> files.
> > >> > It's ok to get default values and the arch name from Config but
> it's
> > not
> > >> > OK to depend on it for probing the system as the Configure code
> will
> > >> > liked be compiled down to PIR someday so it can be executed by
> > >> > miniparrot and systems that don't have perl5 installed.
> > >> >
> > >>
> > >> We've long recognized that we will eventually have to jettison
> our
> > >> reliance on Perl 5's Config module, not just for header detection
> but
> > >> for all of our configuration probes.  But that's a post-1.0
> project.
> > >
> > > Are we closing all bugs for things that aren't going to be part of
> a 1.0
> > > release?
> > >
> > > -J
> > >
> > > --
> > >
> >
> > We shouldn't be closing things solely for that reason, no.
> >
> > --
> > Will "Coke" Coleda
> 
> 
> Maybe it'd be good to add these tickets to trac, planned for a certain
> release. That way, their status and future plans are documented
> better, and
> it will prevent future confusion as activity of the project members
> will
> vary over time (new people joining, others disappearing, etc.)
> 
> just a thought.
> kjs

Good idea; Issue now being tracked at https://trac.parrot.org/parrot/ticket/1202; further 
followups there.

Thanks.

-- 
Will "Coke" Coleda


More information about the parrot-dev mailing list