info > Dpkg::Vendor

man perldoc info pydoc3 ri search

Not found locally for Dpkg::Vendor. Try Google search

The user wants me to transform this Perl man page (Dpkg::Vendor) into an emoji-rich HTML version. Let me carefully follow all the rules: 1. No

- start from

2. Section titles →

with ONE emoji prefix 3. Sub-sections →

with emoji prefix 4. Code in

 blocks
5. No emoji inside code blocks
6. Standard 
/
 for lists
7. Function references use 
name(args) — description
 without per-item emoji
8. Escape < and > outside allowed tags
9. Output only valid HTML
10. Preserve all original information
11. Add 🚀 Quick Reference section as second section
12. Add Exit Codes only if listed (it's not)

Let me look at the original content:
- NAME: Dpkg::Vendor - get access to some vendor specific information
- DESCRIPTION: explains origins files
- FUNCTIONS: list of 6 functions
- CHANGES: 2 version entries
- SEE ALSO: deb-origin(5)

For Quick Reference, I'll generate common use cases:
- Get current vendor name
- Get vendor info fields
- Get vendor directory
- Run vendor hook

Let me build the HTML carefully:

The DESCRIPTION has two code blocks showing origin file format. I need to put them in 
. But wait - the original code contains URLs like https://www.debian.org/ - these are not in  tags in the source, but they're being rendered as links. Looking more carefully, the original input has `https://www.debian.org/` as HTML links. But in code blocks, I should NOT have  tags per rule 8.

Wait, let me re-read rule 8: "Code blocks MUST contain EXACT original code — NO changes, NO added links, NO emoji inside 
. NEVER put  inside a 
 block."

So if these are in 
, I should remove the  tags and just have the raw URL. But the original shows them as links. This is tricky. Looking at the actual content - the URLs are inside what appears to be config file content (Vendor: ..., Vendor-URL: ..., Bugs: ...). The links are documentation-added, not part of the actual config file syntax. So in the code block I should have just the raw URLs.

Actually, looking more carefully, these are example files showing what an origins file looks like. The URLs would normally just be plain text in the config file. So putting them as plain URLs in 
 makes sense.

Let me think about the functions list - it's a perldoc-style function reference, so I should use the 
name(args) — description
 format WITHOUT per-item emoji (per rule 12).

Let me write the HTML now.

For the 🚀 Quick Reference table:
- Use Case | Command | Description
- Rows:
  - Get current vendor name | get_current_vendor() | Returns name of the current vendor
  - Get vendor info object | get_vendor_info($name) | Returns Dpkg::Control object with vendor fields
  - Get vendor directory | get_vendor_dir() | Returns path to origins directory
  - Get vendor object | get_vendor_object($name) | Returns the Dpkg::Vendor::* object
  - Check vendor file | get_vendor_file($name) | Returns file name for vendor
  - Run vendor hook | run_vendor_hook($hookid, @params) | Runs hook on current vendor

Let me also handle XSS - I need to escape any < or > in code that aren't part of allowed tags. Looking at the code: `$dir = get_vendor_dir()` - the ` would need escaping. But since I'm putting these in 
 blocks as raw text (no link), I just write the URL as plain text.

Let me write the output now. The page already has a title structure, so I'll skip 
.

Sections:
1. NAME
2. 🚀 Quick Reference
3. DESCRIPTION
4. FUNCTIONS
5. CHANGES
6. SEE ALSO

For CHANGES, it has sub-entries (Version 1.01, Version 1.00). These are not really sub-sections with their own headings - they're entries in a list. I could use 
 for them, or just use a list format. Looking at rule 3: "Sub-sections within a section → 
 with emoji prefix". The "Version 1.01 (dpkg 1.17.0)" could be an 
. Let me do that.

Actually, looking at this more carefully - the changes section has these as headers (they're indented in the original man page). I'll make them 
.

Let me finalize:

```html
📛 NAME
Dpkg::Vendor - get access to some vendor specific information

🚀 Quick Reference

...

Use Case
Command
Description

📖 DESCRIPTION
...
Vendor: Debian
Vendor-URL: https://www.debian.org/
Bugs: debbugs://bugs.debian.org
...
Parent: Debian
...

⚙️ FUNCTIONS

get_vendor_dir() — Returns the current dpkg origins directory name, where the vendor files are stored.
get_vendor_info($name) — Returns a Dpkg::Control object with the information parsed from the corresponding vendor file in $Dpkg::CONFDIR/origins/. If $name is omitted, it will use $Dpkg::CONFDIR/origins/default which is supposed to be a symlink to the vendor of the currently installed operating system. Returns undef if there's no file for the given vendor.
...


🔄 CHANGES
🆕 Version 1.01 (dpkg 1.17.0)
New function: get_vendor_dir().

📦 Version 1.00 (dpkg 1.16.1)
Mark the module as public.

🔗 SEE ALSO
deb-origin(5).
```

Wait, for the DESCRIPTION's prose paragraphs, I need to be careful. The original has flow text. Let me preserve that.

For the "FUNCTIONS" section - the original uses indented code-like formatting for function signatures. I should convert them to 
... format per rule 12.

Let me also note - in the description of get_vendor_info, it mentions "Returns a Dpkg::Control object" - the original has this as a link. I should preserve that. But inside 
 it's fine to have  tags. Looking at original: `Dpkg::Control` - I should preserve this link. But the  tag isn't in my allowed list... let me check rule 17: "Preserve , ,  tags from the original — they carry semantic meaning."

OK so  is preserved. Good. Allowed tags include .

Let me write the final version. I need to be careful with the description of the vendor file format - the URL line should be raw text inside 
.

Original code block:
```
  Vendor: Debian
  Vendor-URL: https://www.debian.org/
  Bugs: debbugs://bugs.debian.org
```

In code block (no links):
```
Vendor: Debian
Vendor-URL: https://www.debian.org/
Bugs: debbugs://bugs.debian.org
```

Wait, looking again - the indentation in original looks like it's all indented (with spaces). Let me check... yes the original shows indentation. I'll preserve that.

OK let me write the output now.

📛 NAME
Dpkg::Vendor - get access to some vendor specific information

🚀 Quick Reference

Use Case
Command
Description
Current vendor name
get_current_vendor()
Returns name of the active vendor (honors DEB_VENDOR)
Vendor info fields
get_vendor_info($name)
Returns a Dpkg::Control object parsed from the vendor file
Vendor origins dir
get_vendor_dir()
Returns the directory holding vendor files
Vendor object
get_vendor_object($name)
Returns the Dpkg::Vendor::* object
Check vendor file
get_vendor_file($name)
Returns filename if vendor exists
Run vendor hook
run_vendor_hook($hookid, @params)
Invokes a hook on current vendor


📖 DESCRIPTION
The files in $Dpkg::CONFDIR/origins/ can provide information about various vendors who are providing Debian packages. Currently those files look like this:

  Vendor: Debian
  Vendor-URL: https://www.debian.org/
  Bugs: debbugs://bugs.debian.org

If the vendor derives from another vendor, the file should document the relationship by listing the base distribution in the Parent field:

  Parent: Debian

The file should be named according to the vendor name. The usual convention is to name the vendor file using the vendor name in all lowercase, but some variation is permitted. Namely, spaces are mapped to dashes (-), and the file can have the same casing as the Vendor field, or it can be capitalized.

⚙️ FUNCTIONS

get_vendor_dir() — Returns the current dpkg origins directory name, where the vendor files are stored.
get_vendor_info($name) — Returns a Dpkg::Control object with the information parsed from the corresponding vendor file in $Dpkg::CONFDIR/origins/. If $name is omitted, it will use $Dpkg::CONFDIR/origins/default which is supposed to be a symlink to the vendor of the currently installed operating system. Returns undef if there's no file for the given vendor.
get_vendor_file($name) — Check if there's a file for the given vendor and returns its name.
get_current_vendor() — Returns the name of the current vendor. If DEB_VENDOR is set, it uses that first, otherwise it falls back to parsing $Dpkg::CONFDIR/origins/default. If that file doesn't exist, it returns undef.
get_vendor_object($name) — Return the Dpkg::Vendor::* object of the corresponding vendor. If $name is omitted, return the object of the current vendor. If no vendor can be identified, then return the Dpkg::Vendor::Default object.
run_vendor_hook($hookid, @params) — Run a hook implemented by the current vendor object.


🔄 CHANGES
🆕 Version 1.01 (dpkg 1.17.0)
New function: get_vendor_dir().

📦 Version 1.00 (dpkg 1.16.1)
Mark the module as public.

🔗 SEE ALSO
deb-origin(5).