Re: Uniqueness of .deb versions/filenames over distributions
Paul Wise <pabs@debian.org> wrote:
>> - Must .deb versions/filenames be unique over all distribu-
>> tions or is it sufficient if package_0.1_amd64.deb is
>> unique in a distribution (and thus there is an error in
>> aptly)?
> I guess by distributions you mean suites. It depends on the layout of
> your repository but most repositories have a shared pool rather than
> suite-specific pools, so files with the same name must contain
> identical data.
I mean it in a more general sense, ignoring the workflow of
individual tools: Do Debian users expect
package_0.1_amd64.deb to refer to exactly the same binary
package everywhere, or do they expect it to be "bespoke" to
the "environment" it is used in?
>> - If they must be unique over all distributions, what is the
>> best practice for debian/* in that case? AFAICS, one
>> could consider the package for Precise a "backport" and
>> follow the versioning scheme for backports, but I would
>> like (very much) to keep one combined source repository.
> I expect backports is the way to go.
Do you know of Debian packages that combine multiple target
suites in a single debian/* and "amend" the version per tar-
get?
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.BRANCH.NAMING
recommends using different Git branches for jessie, stretch,
etc., but I fear that such a layout could easily cause them
to go out of sync as it puts the burden on the committer to
repeat his changes on another branch.
Tim
Reply to: