smira

Thanks, looks really interesting!

At the moment working on REST API for aptly which should allow similar simple publishing scenarios.

aptly can do more much more than just S3 publishing: for example snapshotting, combining packages from different sources.

I use fpm to build aptly .deb packages, it is extremely simple to use compared to usual source package + build path.

This is a problem for Go programs, due to multiple unversioned (usually) dependencies on other Go libraries.

It is actually available: https://github.com/aptly-dev/aptly-dev.github.io/tree/trunk

In trunk branch, the markdown under content/ folder.

Thanks for your suggestions!

NixOS is aiming for the same goal, I believe. NixOS is built on top of different package manager, Nix.

With aptly you're still using your favorite Debian/Ubuntu distro, installing packages with apt-get and so on.

Sorry for my bad English.

Does this sound better:

"Linux distribution is a well-tested collection of packages that are carefully organized and supported by the vendor."

olgeni, I thought aptly would be useful even if you use only upstream repositories: they get updates and sometimes you don't want all updates to be installed (or you would like to control exact moment to install those updates).