| Summary: | New port: lang/mcc18-wrapper | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Jason W. Bacon <jwb> | ||||
| 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
Jason W. Bacon
2008-12-18 22:50:01 UTC
Responsible Changed From-To: freebsd-ports-bugs->amdmi3 I'll take it. Where did you get the notion that they can't access files outside the Wine dir? I've been using these scripts to build a project in /home/bacon/VexCode. You can try it yourself: http://personalpages.tds.net/~jwbacon/Ports/distfiles/VexCode.tar.gz Yes, the scripts are simple, but learning how to make MCC or any other Windows app work is not trivial for newbies, and the port serves as a guide. -J Dmitry Marakasov wrote: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=129743 >> > > I don't really see the need for this port. > It's just one line scripts and it doesn't make any utils look native, as > they won't be able to access files outside wine dir. > > State Changed From-To: open->closed I was wrong stating that wine apps can't access files outside wine dir (it's just that I've removed links to ~/ and Z: drive pointing to /). Still, I don't see much of use in this port - it relies on apps installed in wine, it relies on wine config, it's way too simple (one will more likely just run `wine mcc18 <filename>` than search for the port). Sorry. |