-
-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate checksums for all Components files [$15] #384
Comments
As long as Aptly reads the |
I'm changing this issue's scope to copy files and generate checksums for all Currently:
Expected behavior:
|
I also put a $15 bounty on this for anyone who want's to add it: |
Just something to add before it gets forgotten: The same thing needs to be done with the |
Bumped the bounty to a total of $50 :) |
I have been looking into this, alas, it is a bit tricky. I'd absolutely love some input on this @smira We need a bunch of information which could be different per source/publishedrepo/usecase.
With that in mind I am currently thinking about the following changes to make this happen: api/publish.go for both initial publishing and updating gets a new attribute AppStream: {} with the aforementioned attributes for appstream-generator.
We probably ought to mangle this information internally a bit more. MediaBaseURL for example should probably be expanded to be "prefix-unique" by appending the actual publishing prefix, so what we give to asgen would be
To that end
This should give us a largely working lineup for local repositories. How to deal with remote publishing endpoints I am not really sure to be honest. All of this also assumes that some other piece of software grabs $AptlyRoot/asgen/$Prefix/export/media (i.e. the screenshots) to publish them under the URL we were provided. We will probably also need some global .aptly.conf option to configure an appstream-generator run string so that one can "intercept" and redirect the appstream-generator run (e.g. to run in a container, or on a different host). Running appstream-generator on the same system as aptly is a bit meh from a security POV. |
It would be amazing if aptly would generate AppStream data when it publishes a repository. This would allow packages in the published repo to be seen by new-age app centers, including gnome software.
Here is a generator written in D for reference.
The text was updated successfully, but these errors were encountered: