(Dual reply to two emails)
On 30 December 2021 at 23:32, Wookey wrote:
| On 2021-12-26 18:08 -0600, Dirk Eddelbuettel wrote:
| >
| > Does anybody know where we are with respect to the WNPPs / ITPs / ... on the
| > Amazon SDK for C++?
| >
| > I have a package that could take advantage of this if it were packaged, and I
| > am sure a number of other packages are in a similar situation given how
| > pervasive AWS use is.
|
| I don't know anything about the state of this, but am in the same
| place, in that I am packaging something that uses awsSDK pieces,
| specifically tensorflow which wants aws-cpp-sdk-core.
|
| > FWIW I have packaged _subsets_ of the C++ SDK informally for my own use (also
| > at Launchpad) but I don't think I have the time and energy to take this on as
| > another package.
|
| Which bits have you done? They may or may not be sufficient to satisfy tensorflow.
In Debian testing (via informal 'PPA for testing' on GitHub) and for focal
via ppa:edd/misc
edd@rob:~/git/ppa/docs(master)$ ls -1 libaws*deb # omitting double entries libaws-c-common-dev_0.4.59-1.debian.1_amd64.deb libaws-c-event-stream-dev_0.1.6-1.debian.1_amd64.deb libaws-checksums-dev_0.1.9-1.debian.2_amd64.deb libaws-sdk-cpp-only-s3-dev_1.8.117-3.debian.1_amd64.deb edd@rob:~/git/ppa/docs(master)$
edd@rob:~$ dpkg -l | grep libaws | cut -c-80
ii libaws-c-common-dev 0.4.59-1.2004.1
ii libaws-c-event-stream-dev 0.1.6-1.2004.1
ii libaws-checksums-dev 0.1.9-1.2004.1
ii libaws-sdk-cpp-only-s3-dev 1.8.117-1.2004.1
edd@rob:~$
| I too, am not bursting to add large packages that I don't use (or even
| properly know what they are) to my collection of responsibilities, but
| I can spend work time on helping get this going so I don't mind
| mucking in on some packaging work.
Great!
On 30 December 2021 at 22:17, Ross Vandegrift wrote:
| On Mon, Dec 27, 2021 at 08:10:50AM -0600, Dirk Eddelbuettel wrote:
| > My (very informal) packaging has always been in the open (but on GitHub). A | > possible first step might be to review the added files in debian/ and in a | > first pass edit out all references to 'informal' or 'unofficial' packaging | > and making them more official in the cloud team repo -- which I presume is on
| > salsa? If you or others want to look, I have this currently at github.com in
| >
| > eddelbuettel/pkg-aws-c-common common C layer
| > eddelbuettel/pkg-aws-checksums checksum for transport
| > eddelbuettel/pkg-aws-c-event-stream another C layer
| > eddelbuettel/pkg-aws-sdk-cpp-only-s3 C++ SDK subset for S3
|
| I did some work on aws-c-common & aws-c-event-stream from a PoC of packaging | for awscli v2. Details are in #966573, message 43 [1].
|
| So far, I haven't uploaded any of this. The AWS SDK now requires their own
| crypto & tls implementations. The cloud team discussed this a while back, no | one found that responsibility very attractive. Still, we'll want awscli v2
| eventually.
I think in what I need the crypto etc comes from curl and openssl as usaul.
| > The last repo is the one that is 'incomplete' as I skipped everything not
| > need by my use case of accessing s3 programmatically from other C++ code.
| > >From a casual look at another C++ project I noticed that it had the same
| > subset so this may make sense. It would allow us to proceed and start with | > the subset and add as needed (as opposed to be overwhelmed by 'all of it'). |
| I'd be worried about confusing users who expect to have the whole SDK
| available. But as long as the packages only ship static libraries, I don't see
| how it would cause actual issues.
Right on with the name and confusion so I picked 'libaws-sdk-cpp-only-s3-dev' to signal the subset nature, at least for now.
Dirk
--
https://dirk.eddelbuettel.com | @eddelbuettel |
edd@debian.org
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)