#712: Some changes are needed to the install system so that Parrot installs in a
fashion that's useable by Rakudo
---------------------+------------------------------------------------------
Reporter: wayland | Type: patch
Status: new | Priority: normal
Milestone: | Component: none
Version: trunk | Severity: medium
Keywords: | Lang:
Patch: new | Platform:
---------------------+------------------------------------------------------
Changes (by jkeenan):
* cc: jkeenan (added)
* type: bug => patch
* patch: => new
Comment:
I'm skeptical of the attached patch largely because I'm skeptical that
using ''MANIFEST.configure.generated'' should be used in the install
programs -- and I'm the person who introduced
''MANIFEST.configure.generated'' into the Parrot distro in the first
place!
A bit of history here: Back in November 2006, particle filed
[http://rt.perl.org/rt3/Ticket/Display.html?id=40817 RT #40817: track
generated files during the configure/make process]. No one did anything
about the ticket for the next 16 months. I had been doing a lot of testing
and refactoring of the configuration system, so I took a crack at an
'''intermediate step''': tracking those files that were generated while
''Configure.pl'' was running. The result was
`Parrot::Configure::Compiler::append_configure_log()` and
''MANIFEST.configure.generated''. But I didn't know how to conduct the
'makefile trickery' that particle suggested would be needed to track files
generated while ''make'' is running. So that RT was never fully solved,
even though recently I closed it and replaced its unsolved parts with TT
#677
So ''MANIFEST.configure.generated'' wasn't intended to be used by the
install programs. Indeed, at the time I created it, I had never looked at
the install programs. So any usefulness it may have as part of the
install process is purely accidental.
Moreover, as I have discussed in TT #677, it's not simply a question of
figuring out what files ''Configure.pl'' and ''make'' generate. We also
need to determine a reliable way of assigning to those files the metadata
needed by the install programs. Most of the generated files do not end up
getting installed.
I don't claim to have studied the patch thoroughly yet. All I'm saying is
that ''MANIFEST.configure.generated'' is perhaps not the way to go.
Thank you very much.[[BR]]
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/712#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
