Tasks #800
Discuss package names
| Status: | Closed | Start date: | 01/13/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Robotics Service Bus - rsb-0.9 |
Description
We should discuss the package names on the package server.
Most of the packages named as follows <PROJEKT-NAME>0.3-0.3.0_lucid_i686.deb
- Why is the version number included twice?
- Is there a reason for that?
- Could we find a more simplified naming schema?!
History
#1 Updated by J. Moringen over 12 years ago
The general scheme seems to be as follows
The Debian binary package file names conform to the following convention:
<foo>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.deb
In case of co-existing major versions (e.g. Python 2.6 and Python 3.0) <foo> has to contain the major version (e.g. <foo> = python2.6) in order to independently maintain theses packages and make them selectable in packaging tools.
#2 Updated by J. Moringen almost 12 years ago
- Target version set to rsb-0.9
#3 Updated by J. Wienke almost 12 years ago
Will we ever be able to resolve this issue or should we just close it and reopen of we find something more concrete after the last discussions?
#4 Updated by J. Moringen about 11 years ago
- Status changed from New to Feedback
We pretty much agreed on this now, didn't we? I think, we can close this issue.
#5 Updated by J. Moringen almost 11 years ago
- Status changed from Feedback to Closed