pool locations should be handled automatically and dirhashed
Currently when adding content you must tell the pulp_deb plugin what the relative path is. While the ability to specify this is useful, by default, it should create hashed pool directories ala the debian/ubuntu official repos:
I would expect to add content called `foo_1.0-1_amd64.deb` and at the very least have the default path be:
In a typical apt repo, it would be something like:
But I think Pulp would prefer packages to be able to be associated with multiple repos, thus having the distribution not be part of the content path makes sense.
Add file upload functionality to content types
re #5403 https://pulp.plan.io/issues/5403 fixes #5487 https://pulp.plan.io/issues/5487 fixes #5371 https://pulp.plan.io/issues/5371 fixes #5376 https://pulp.plan.io/issues/5376 fixes #5379 https://pulp.plan.io/issues/5379
Required PR: https://github.com/pulp/pulpcore-plugin/pull/122
#1 Updated by mdellweg about 1 year ago
OK, this one is a little bit odd: There are two publication mechanisms in pulp_deb.
1 Verbatim publication: All files (from all content) are published in the path specified as relative_path; metadata is not generated, but forwarded. That way, you can mirror an upsteam repo (including the original signatures).
2. Simple publication: All packages are published in a single repo component. This time, the publication paths for the packages are generated in the way you described. Metadata is generated (and hopefully in the future signed).
A more complex method for publishing is planned, but it is yet to be determined how to save the necessary data.
Please register to edit this issue