#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:  install
  Version:  trunk    |    Severity:  medium 
 Keywords:           |        Lang:         
    Patch:  new      |    Platform:         
---------------------+------------------------------------------------------

Comment(by wayland):

 Hmm.  A few things:
 - I admit that I've kind of dropped out of the Parrot and Rakudo
 communities for a bit, and don't expect to be back before December.  The
 only thing I'm sure of is that when last I tried to build an RPM of
 parrot, it didn't work just by getting the release and trying to build it
 with the spec file.  So the spec file certainly needs to be fixed in some
 way.
 - You'll notice that all the changes outside the spec file are directed at
 getting files in runtime/parrot/include to be included in the spec file

 After I made this patch, kid51 and I had some discussions about how things
 should be done.  My big plan was to make a library for reading and writing
 MANIFEST files, and then calling on that from all the places that need
 that (apparently we have duplicate code doing that, but the duplicate code
 doesn't match 100%, which is probably a bad thing).  IIRC, kid51 wasn't so
 keen on that, and also said that there was a big discussion coming up on
 the subject (unless I'm confusing this with something else).  But if I've
 remembered correctly, kid51 and I decided just to sit on this ticket until
 it had been sorted out whether/how to do a MANIFEST reading/writing
 library.

 What needs to happen on this is:
 - I need to get back into Parrot/Rakudo
 - kid51 and I need to revisit the issue together

 An alternative would be for someone to try to understand why I created the
 patch in the first place, since I've forgotten why (having not installed
 Parrot in about 4 months now).  As a step towards that, does anyone know
 why the files in runtime/parrot/include might be needed?  Pmichaud?
 Someone?  Help! :)

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/712#comment:6>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to