I removed the aws-sdk-cpp package in Bug #845654, but I think it would be best to also remove the packages that this package depended on. dev-libs/aws-c-common dev-libs/aws-c-event-stream dev-libs/aws-checksums No other packages depend on these packages. Reproducible: Always
Please don't CC arches for generic bugs.
Sorry about that.
To clarify the packages that needed to be addressed, we created a bug related to the packages that the aws-sdk-cpp package depended on. Bug 908094 dev-libs/aws-c-common : cleanup or bump ebuilds Bug 908095 dev-libs/aws-c-event-stream : cleanup or bump ebuilds Bug 908096 dev-libs/aws-checksums : cleanup or bump ebuilds Bug 908097 dev-libs/s2n : cleanup or bump ebuilds
Thank you!
Two related package bugs have been added. Bug 908428 dev-libs/aws-c-io: cleanup or bump Bug 908427 dev-libs/aws-c-cal: cleanup or bump
I'm thinking of using the GURU repository to manage aws-sdk-cpp once I have finished cleaning up the dependent libraries of aws-sdk-cpp, but in that case, should I register the libraries that only this package depends on as separate libraries? Or should we build them together? The current AWS SDK CPP version 1.11 has the ability to build aws dependent libraries at the same time.
(In reply to trakrailysurely from comment #6) > I'm thinking of using the GURU repository to manage aws-sdk-cpp once I have > finished cleaning up the dependent libraries of aws-sdk-cpp, but in that > case, should I register the libraries that only this package depends on as > separate libraries? I suggest you package them separately. At least one other program (awslabs/mountpoint-s3) depends on yet-to-be-packaged AWS CRT libraries. I'm interested in helping you package/maintain the AWS CRT if you want to, because I want to provide the aforementioned mountpoint-s3 :^) I have time starting from October.
> I want to provide the aforementioned mountpoint-s3 For the time being, I'm no longer interested in maintaining this package and its dependencies.
