Skip to content
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

Relationship between a Debian source and binary package #1185

Open
Urist-McGit opened this issue Feb 18, 2025 · 1 comment
Open

Relationship between a Debian source and binary package #1185

Urist-McGit opened this issue Feb 18, 2025 · 1 comment
Labels
question Request for information or clarification

Comments

@Urist-McGit
Copy link

In the Debian ecosystem each binary package references a source package from which it is built. To quote from the documentation:

Source packages provide you with all of the necessary files to compile or otherwise, build the desired piece of software.

It consists, in its simplest form, of three files:

    The upstream tarball with .tar.gz ending

    A description file with .[dsc](https://wiki.debian.org/dsc) ending. It contains the name of the package, both, in its filename as well as content (after the Source: keyword).
    A tarball, with any changes made to upstream source, plus all the files created for the Debian package.

        This has a .debian.tar.gz (source format : 3.0)

        or a .diff.gz ending (source format : 1.0)

We are unsure how to exactly represent the relationship between these two packages. Candidates would e.g. be GENERATES, PREREQUESITE_FOR. Is there already a consensus what is best? What would you recommend?

@bact bact added the question Request for information or clarification label Feb 18, 2025
@goneall
Copy link
Member

goneall commented Feb 25, 2025

My suggestion would be GENERATES if the binary package is created from the source files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Request for information or clarification
Projects
None yet
Development

No branches or pull requests

3 participants