Standard version specification in Dockerfile's for 'x-pkg verrel'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey y'all,

I'm a developer at Red Hat working on adding a user-requested feature to the 'x-pkg' line of products.
Specifically, the user would like the 'x-pkg verrel' command to work for those projects under the 
container/* branch of Fedora targeted software in the same way that the command works for 
rpm/ software.

issue: https://pagure.io/rpkg/issue/547

However, different container maintainers include the metadata about their Dockerfile's in different ways.
Take nginx for example. Its Dockerfile contains both:

NGINX_VERSION=1.12

and 

VERSION=0

What would be the correct way to solve this collision for a hypothetical workflow that you might have?
Are there any ad hoc best-practices w.r.t Dockerfile standards involving specifying the version and release 
number?

Any feedback or suggestions would be helpful.

-jkunstle
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux