Bug 196434
| Summary: | [NEW PORT] net/p5-Amazon-S3: Portable client library for working with Amazon S3 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | gebhart | ||||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||||
| Status: | Closed Overcome By Events | ||||||||
| Severity: | Affects Many People | CC: | sunpoet | ||||||
| Priority: | --- | Keywords: | feature, needs-qa, patch | ||||||
| Version: | Latest | ||||||||
| Hardware: | Any | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
Created attachment 152312 [details]
update port shar (1 dependency missing)
Added a missing dependency (www/p5-LWP-UserAgent-Determined). shar file updated.
Something wrong with this port ? Is it because of the suggested removal of another port? You can also keep that one, they don't interfere with each other. I just wondered, because new ports I created and submitted later are in the ports tree for weeks now. (In reply to gebhart from comment #0) You mentioned that "net/p5-Net-Amazon-S3 is too old to work with the current S3 architecture" but it seems to be reversed. According to CPAN, net/p5-Net-Amazon-S3 0.80 was released on Apr 11, 2015 and net/p5-Amazon-S3 0.45 was released on Aug 14, 2009. It shows that p5-Amazon-S3 (this port) is much older. Could you please explain more about that? Thanks. I guess, we can close/forget this. See the dates. My last message was before the new release of net/p5-Net-Amazon-S3. The versions before that did not work, but obviously someone picked up the problem. p5-Amazon-S3 is dead slow, but was the only working implementation at that time, that's why I made a port. |
Created attachment 151206 [details] actual port files Unlike net/p5-Net-Amazon-S3 this new port really works with Amazon's S3. net/p5-Net-Amazon-S3 is too old to work with the current S3 architecture and can be removed.