Bug 126724
| Summary: | New port: devel/psptoolchain PlayStation Portable development tools | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Tassilo Philipp <tphilipp> | ||||
| Component: | Individual Port(s) | Assignee: | Dmitry Marakasov <amdmi3> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
Tassilo Philipp
2008-08-22 01:10:02 UTC
Responsible Changed From-To: freebsd-ports-bugs->amdmi3 I'll take it. State Changed From-To: open->feedback Awaiting feedback Hi! > Synopsis: New port: devel/psptoolchain PlayStation Portable development tools The port seem to fetch and build things during install stage. This is unacceptable. Actually, the whole thing won't live well as a port as it is. The good way would be to make a separate port out of each script under scripts/. This should be pretty straightforward, as each script does very same things that a typical port would do (fetch, extract, patch, configure, build & install). See ports/devel/avr-* as an example of cross toolchain. Another way is to just install the whole psptoolchain into some directory, so user may run a script and have toolchain compiled. But, since there are almost no freebsd-specific changes I don't see a purpose in such a port. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru Hm, I understand... So with the "good way", basically you're saying that a port for each script under scripts/ should be available, building that port during the make stage? So, in the end we basically don't need the scripts anymore that are provided with the toolchain, and do the same things the scripts do via the ports' Makefile? >> Hm, I understand... So with the "good way", basically you're saying that >> a port for each script under scripts/ should be available, building that >> port during the make stage? So, in the end we basically don't need the >> scripts anymore that are provided with the toolchain, and do the same >> things the scripts do via the ports' Makefile? > Correct. Ok, I'll try to do it that way, then. This might take me a couple of days, though. Thanks! State Changed From-To: feedback->closed Submitter is working on multi port version of toolchain; port submitted in this pr is of no use, close. |
