#442: Can't build a well-behaved Rakudo RPM without being able to specify system
library paths
---------------------+------------------------------------------------------
Reporter: wayland | Type: feature
Status: new | Priority: normal
Milestone: | Component: none
Version: 0.9.1 | Severity: medium
Keywords: | Lang:
Patch: | Platform:
---------------------+------------------------------------------------------
Comment(by doughera):
Thank you for the nice explanation. I had looked in docs/running.pod to
try to understand the purpose of these command-line options. Silly me.
(Calling it a "system library path" instead of the "dynamic extensions
path" also confused me.) I do not know what specific RPM problems you
encountered, but there might be other ways around those problems.
Anyway, yes. I see your point that if there are three different paths,
then parrot indeed needs three different options.
However, while those options ought to be available, they also ought not to
be necessary for this case.
You ought to be able to configure parrot to put things where you want them
in the first place. There ought to be appropriate Configure.pl command-
line options to set each of those three paths independently.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/442#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
