• The 'Source' field in DEP 5

    From Akbarkhon Variskhanov@21:1/5 to All on Sat Nov 12 18:40:02 2022
    Hi.

    I know that this format is optional but I was wondering what exactly
    this field is expected to include. In my interpretation, it's a URL to
    a directory containing upstream tarballs, say https://www.example.com/src/download. However, I've also seen people
    put links to upstream Git repositories. Which one is closer to the
    definition and is preferred over the other? Technically, *the* source
    is the Git repository but if we're talking about packaged releases,
    tarball is the source to which the current debian/copyright file
    applies. It seems to me that both interpretations may be deemed valid.
    Was that intentional? Could you perhaps clarify it a little bit?

    Many thanks.

    Regards,
    Akbar.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Francesco Poli@21:1/5 to All on Fri Nov 18 00:00:01 2022
    On Sat, 12 Nov 2022 22:13:11 +0500 Akbarkhon Variskhanov wrote:

    Hi.

    Hello!


    I know that this format is optional but I was wondering what exactly
    this field is expected to include. In my interpretation, it's a URL to
    a directory containing upstream tarballs, say https://www.example.com/src/download. However, I've also seen people
    put links to upstream Git repositories. Which one is closer to the
    definition and is preferred over the other?

    The official [documentation] says:

    [...]
    | 6.4. Source
    |
    | Formatted text, no synopsis: an explanation of where the upstream
    | source came from. Typically this would be a URL, but it might be a
    | free-form explanation. The Debian Policy section 12.5 requires this
    | information unless there are no upstream sources, which is mainly the
    | case for native Debian packages. If the upstream source has been
    | modified to remove non-free parts, that should be explained in this
    | field.
    [...]

    [documentation]: <https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#source-field>

    I interpret it to mean that you should use this field to explain where
    you took the upstream source from. Basically, whatever you started from,
    in order to create the Debian package.

    Technically, *the* source
    is the Git repository but if we're talking about packaged releases,
    tarball is the source to which the current debian/copyright file
    applies. It seems to me that both interpretations may be deemed valid.
    Was that intentional? Could you perhaps clarify it a little bit?

    I think it's flexible enough to accommodate for any specific case.

    Anyway, I am _not_ one of the people who were involved in the drafting
    of the machine readable debian/copyright format specification.
    Maybe one of those people can clarify better than me...

    I hope this helps.


    --
    http://www.inventati.org/frx/
    There's not a second to spare! To the laboratory! ..................................................... Francesco Poli .
    GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEygERR5zS79/7gjklPhwn4R9pv/4FAmN2u48ACgkQPhwn4R9p v/6tHg//RUzZURqdgC1sF1vW87M0gYClQ2c92qy+YADm/lZaOF5mmR/nx+EG6Toe XYswOpTZHs6s8y91YGrlmg2gOBl7RhqaBkccW8uXK4e/E4ohjPxIJgWVMmO4Hf/3 WizvvRXjQzyOdmA7G4rtaVRLZJMqWJuXvRPrSZlGr0LWdVit4uvdffXjwLBge8Hw TgdDLd1NKO7phtlkIDOQ8ity1ZPqiiIMpliylGDoZcMd4j+E6orTshxgUF+9BBkj Pat8E0nLQlBxXJX8BywpAjjovls2QDGH/FyxzarC9Dosp/nVvrKOn//OECQqaLPA 6k/aPM3m9So4kVx84sRETN59REfhbieiB7kiK+YBYMrYrijuE2Bth2ZMYW+z6WlC ZrisSWMr30zGCulhpU/XFaZ+aScWSl6kEykrngdtg72CCX4t5FHZauBt7RdVO9Wt qj9B65M2DdF5yg1Rnq5C/Y/Oo4c/iz2YEgaGBHhpiR8IYtEbq9gZMxz4NVgHyi0f EU7tQUKi6QSaP6Uz6vRizK/EsN1L5uoHZrRMWtejwes5EDzgy9zwl0DZGxDdeNYb jdZge4ykEDtqYsMPz5LHxNxNlkK5HqxAByNw1BXB/2QGc6s0L7AX9JkEr+QSk+VZ RsVomh1QCXNOxO9hnZZ76bOALGjrZiYI