Bug 178324 - [Update] games/frogatto to 1.3.1
Summary: [Update] games/frogatto to 1.3.1
Status: Closed DUPLICATE of bug 190469
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Alexey Dokuchaev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-03 18:40 UTC by fiziologus
Modified: 2014-06-11 15:04 UTC (History)
1 user (show)

See Also:

Attachments
file.txt (55.14 KB, text/plain)
2013-05-03 18:40 UTC, fiziologus 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description fiziologus 2013-05-03 18:40:00 UTC 
[games/frogatto] Update to 1.3.1

Now use pkg-plist instead PLIST

Fix: Patch attached with submission follows:
Comment 1 Alexey Dokuchaev freebsd_committer freebsd_triage 2013-05-10 12:10:59 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->danfe

I'll handle it...
Comment 2 Alexey Dokuchaev freebsd_committer freebsd_triage 2013-05-10 12:16:28 UTC 
State Changed
From-To: open->feedback

When I originally created the port, I've decided to use dynamic PLIST (as 
much as I hate them just like anyone else does, as they are non-greppable 
and just evil) because this game installs huge number (thousands) of files. 
Now you're proposing to use static PLIST.  Given the size of your patch, 
and the fact that you had to compress/uuencode it, I assume that static 
pkg-plist would be still as huge. 

May we know, what particular benefits will it bring here that overweight all 
the burden of it (in this case)?  Did you encounter some problem with 
dynamic plist (apart from it being unintuitive)?  Perhaps it could be solved 
without huge static pkg-plist?  Static PLISTs are nice, but when their size 
is sane. :-(
Comment 3 John Marino freebsd_committer freebsd_triage 2014-06-11 15:04:30 UTC 
Danfe, 
Apparently he resubmitted this under another ID: 190469
I don't know why the new patch wasn't just added to this PR.

I'm taking the liberty to close this for you.
John

*** This bug has been marked as a duplicate of bug 190469 ***