Bug 196434 - [NEW PORT] net/p5-Amazon-S3: Portable client library for working with Amazon S3
Summary: [NEW PORT] net/p5-Amazon-S3: Portable client library for working with Amazon S3
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: feature, needs-qa, patch
Depends on:
Blocks:
 
Reported: 2015-01-02 11:15 UTC by gebhart
Modified: 2016-01-05 15:57 UTC (History)
1 user (show)

See Also:

Attachments
actual port files (2.41 KB, text/plain)
2015-01-02 11:15 UTC, gebhart 		no flags Details
update port shar (1 dependency missing) (2.43 KB, text/plain)
2015-01-28 16:17 UTC, gebhart 		no flags Details
Show Obsolete (1) 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 gebhart 2015-01-02 11:15:04 UTC 
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.
Comment 1 gebhart 2015-01-28 16:17:50 UTC 
Created attachment 152312 [details]
update port shar (1 dependency missing)

Added a missing dependency (www/p5-LWP-UserAgent-Determined). shar file updated.
Comment 2 gebhart 2015-03-30 12:29:54 UTC 
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.
Comment 3 Po-Chuan Hsieh freebsd_committer freebsd_triage 2016-01-01 13:14:17 UTC 
(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.
Comment 4 gebhart 2016-01-05 15:57:11 UTC 
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.