You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr (Jira)" <ji...@apache.org> on 2022/11/01 07:52:00 UTC

[jira] [Assigned] (IGNITE-18036) Correct packaging naming

     [ https://issues.apache.org/jira/browse/IGNITE-18036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksandr reassigned IGNITE-18036:
----------------------------------

    Assignee: Aleksandr

> Correct packaging naming
> ------------------------
>
>                 Key: IGNITE-18036
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18036
>             Project: Ignite
>          Issue Type: Task
>          Components: build
>            Reporter: Aleksandr
>            Assignee: Aleksandr
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta1
>
>
> According to conventions, the rpm package should be named 
> {code}
> [name]-[version]-[release].[arch].rpm
> {code}
> deb package
> {code}
> foo_ver-rev_arch.deb
> {code}
> Rename current package names for all distributions:
> - ignite3-cli-3.0.0-beta1.noarch.rpm
> - ignite3-db-3.0.0-beta1.noarch.rpm
> - ignite3-cli_3.0.0-beta1_all.deb
> - ignite3-db_3.0.0-beta1_all.deb
> - docker: apacheignite/ignite3
> - ignite3-cli-3.0.0-beta1.zip
> - ignite3-db-3.0.0-beta1.zip
> - ignite3-3.0.0-beta1.zip
> References
> https://www.linuxtopia.org/online_books/linux_system_administration/debian_linux_guides/debian_linux_reference_guide/ch-system.en_019.html
> https://www.thegeekdiary.com/understanding-rpm-versions-and-naming-schemes/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)