Hi Dave,
I have mostly based the RPM on what Cassandra was doing to distribute RPMs (
http://cassandra.apache.org/download/)
The idea is to have YUM (for RPM) and Apt-Get (for Deb) repositories that
can be added and then packages can be installed automatically, with
checksums and signatures validated.
The `Packages.gz` and `RPMS/repodata` are there to make the directory a
valid repository for packages. These are generated by respective tools:
* For RPMs :
https://github.com/apache/incubator-pulsar/blob/master/pulsar-client-cpp/pkg/rpm/build-rpm.sh#L43
* For Deb :
https://github.com/apache/incubator-pulsar/blob/master/pulsar-client-cpp/pkg/deb/build-deb.sh#L95
Regarding `pulsar-client` vs `apache-pulsar-client` and including
`incubating` in the package release, I've opened a PR to address that
https://github.com/apache/incubator-pulsar/pull/2129
Thanks,
Matteo
On Mon, Jul 2, 2018 at 10:13 AM Dave Fisher wrote:
> Hi -
>
> Pulsar plans to release DEB and RPM convenience binaries and we need to
> discuss the artifacts. How they are named and why each one is required.
>
> My experience with releasing these types of binaries is from OpenOffice
> where we have released DEB and RPM binaries for a long time. See
> http://archive.apache.org/dist/openoffice/4.1.5/binaries/en-US/
>
> Starting from here:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.0-incubating-candidate-4/
>
> Look into both the DEB and RPMS directories and note that both “apache-"
> and “-incubating" are missing from the names. Unless there is good reasons
> that are explained with the explanation accepted then the names need to be
> changed in the next release candidate.
>
> What is “Packages.gz” in the DEB directory? Is that name prescriptive?
>
> Please explain repodata in the RMPS/repodata directory.
>
> Regards,
> Dave
>
--
Matteo Merli
