Home Explore Help
Sign In
NitoTV
/
dpkg
Watch 2
Star 0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Branch: libmissing
Branches Tags
dpkg
/
man
/
deb-origin.man

deb-origin.man 2.4 KB
Permalink History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667 
  1. .\" dpkg manual page - deb-origin(5)
    2. 

  2. .\"
    3. 

  3. .\" Copyright © 2011 Matt Kraai <kraai@ftbfs.org>
    4. 

  4. .\" Copyright © 2011 Guillem Jover <guillem@debian.org>
    5. 

  5. .\"
    6. 

  6. .\" This is free software; you can redistribute it and/or modify
    7. 

  7. .\" it under the terms of the GNU General Public License as published by
    8. 

  8. .\" the Free Software Foundation; either version 2 of the License, or
    9. 

  9. .\" (at your option) any later version.
    10. 

  10. .\"
    11. 

  11. .\" This is distributed in the hope that it will be useful,
    12. 

  12. .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
    13. 

  13. .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    14. 

  14. .\" GNU General Public License for more details.
    15. 

  15. .\"
    16. 

  16. .\" You should have received a copy of the GNU General Public License
    17. 

  17. .\" along with this program.  If not, see <https://www.gnu.org/licenses/>.
    18. 

  18. .
    19. 

  19. .TH deb\-origin 5 "%RELEASE_DATE%" "%VERSION%" "dpkg suite"
    20. 

  20. .nh
    21. 

  21. .SH NAME
    22. 

  22. deb\-origin \- Vendor-specific information files
    23. 

  23. .SH SYNOPSIS
    24. 

  24. .BI %PKGCONFDIR%/origins/ filename
    25. 

  25. .SH DESCRIPTION
    26. 

  26. The files in \fB%PKGCONFDIR%/origins\fP can provide information about
    27. 

  27. various vendors who are providing Debian packages.
    28. 

  28. 

  29. They contain a number of fields, or comments when the line starts with
    30. 

  30. ‘\fB#\fP’.
    31. 

  31. Each field begins with a tag, such as \fBVendor\fP or \fBParent\fP,
    32. 

  32. followed by a colon and the body of the field. Fields are delimited
    33. 

  33. only by field tags. In other words, field text may be multiple lines
    34. 

  34. in length, but the tools will join lines when processing the body of
    35. 

  35. the field.
    36. 

  36. 

  37. The file should be named according to the vendor name.
    38. 

  38. The usual convention is to name the vendor file using the vendor name
    39. 

  39. in all lowercase, but some variation is permitted.
    40. 

  40. Namely, spaces are mapped to dashes (‘\fB\-\fP’), and the file
    41. 

  41. can have the same casing as the value in \fBVendor\fP field, or it can
    42. 

  42. be capitalized.
    43. 

  43. .SH FIELDS
    44. 

  44. .TP
    45. 

  45. .BR Vendor: " \fIvendor-name\fP (required)"
    46. 

  46. The value of this field determines the vendor name.
    47. 

  47. .TP
    48. 

  48. .BI Vendor\-URL: " vendor-url"
    49. 

  49. The value of this field determines the vendor URL.
    50. 

  50. .TP
    51. 

  51. .BI Bugs: " bug-url"
    52. 

  52. The value of this field determines the type and address of the bug
    53. 

  53. tracking system used by this vendor. It can be a mailto URL or a
    54. 

  54. debbugs URL (e.g., debbugs://bugs.debian.org/).
    55. 

  55. .TP
    56. 

  56. .BI Parent: " vendor-name"
    57. 

  57. The value of this field determines the vendor name of the vendor that
    58. 

  58. this vendor derives from.
    59. 

  59. .SH EXAMPLE
    60. 

  60. .nf
    61. 

  61. Vendor: Debian
    62. 

  62. Vendor\-URL: https://www.debian.org/
    63. 

  63. Bugs: debbugs://bugs.debian.org
    64. 

  64. .fi
    65. 

  65. .SH SEE ALSO
    66. 

  66. .BR dpkg\-vendor (1)
    67. 

  67.