info > CVS-DEBI

man perldoc info pydoc3 ri search

Let me analyze this man page for cvs-debi and transform it into an emoji-rich HTML version while preserving structure. The original document has: 1. Name: cvs-debi 2. Synopsis: cvs-debi [options] [package ...] 3. Description 4. Options (with subsections for each option) 5. See Also 6. Author I need to: - Start from

(never

) - Add emoji to section headings - Wrap all code in

- Create a 🚀 Quick Reference section
- Preserve all original content
- Escape any bare < or > characters

Let me check for any code:
- `cvs-debi` - command name
- `cvs-debi [options] [package ...]` - synopsis
- `.changes` - filename
- `.deb` - filename
- `debpkg -i` - command
- `cvs-buildpackage` - command
- `cvs-debuild` - command
- `-P` - flag
- `debpkg` - command
- `dpkg` - command
- `-adebian-architecture`, `-tGNU-system-type` - flags
- `-Mmodule` - flag
- `-Ppackage` - flag
- `-Vversion` - flag
- `-Ttag` - flag
- `-Rroot directory` - flag
- `-Wwork directory` - flag
- `-xprefix` - flag
- `--help`, `--version` - flags

Let me also note:
- The author email has `` - the `` need to be escaped to `<` and `>`
- But it's already partially handled with `` tag. The email is wrapped in an `` so that's fine.

Wait, looking more carefully at the AUTHOR section: `Julian Gilbey <jdg AT debian.org>`

So the `<` and `>` are for the angle brackets around the email. These are already escaped. Good.

Now let me also check the original for any other code that needs 
:
- `debpkg -i` - command
- `dpkg-buildpackage` - command

These should be in  tags at minimum, or 
 if they're standalone.

Let me structure the output:

📛 NAME
cvs-debi - install cvs-buildpackage/cvs-debuild generated package

🚀 Quick Reference
...use cases...

📋 SYNOPSIS
cvs-debi [options] [package ...]

📖 DESCRIPTION
...description...

⚙️ OPTIONS
...options with subsections...

🔗 SEE ALSO
...see also...

👤 AUTHOR
...author...

Let me write this out now, making sure to:
1. Use 
 for all code
2. Add emoji to headings
3. Preserve original , ,  tags where applicable
4. Not add emoji inside 

5. Escape any bare < or >
6. Not wrap comments in code blocks as headings
7. Create Quick Reference table

For the Quick Reference, common use cases would be:
- Install generated package | `cvs-debi` | Install all .deb files from the changes file
- Install specific package | `cvs-debi -P package` | Install only specified package
- Use specific CVS module | `cvs-debi -M module` | Specify CVS module name
- Specify version | `cvs-debi -V version` | Specify package version
- Cross-architecture | `cvs-debi -adebian-architecture` | Set target architecture

Let me finalize this now.

📛 NAME
cvs-debi - install cvs-buildpackage/cvs-debuild generated package

🚀 Quick Reference

Use Case
Command
Description
Install all generated debs
cvs-debi
Install every .deb listed in the .changes file from the current CVS working directory
Install specific package
cvs-debi -P pkgname
Install only the deb(s) matching the given source package name
Target architecture
cvs-debi -adebian-architecture
Locate the .changes file for a specific Debian architecture
Specify CVS module
cvs-debi -M module
Set the CVS module name explicitly
Specify version
cvs-debi -V version
Set the package version number explicitly
Show help / version
cvs-debi --help / cvs-debi --version
Display help message or version information


📋 SYNOPSIS
cvs-debi [options] [package ...]

📖 DESCRIPTION
🔧 cvs-debi is run from the CVS working directory after cvs-buildpackage or cvs-debuild. It uses the cvs-buildpackage system to locate the .changes file generated in that run. It then runs debpkg -i on every .deb archive listed in the .changes file to install them, assuming that all of the .deb archives live in the same directory as the .changes file. ⚠️ Note that you probably don't want to run this program on a .changes file relating to a different architecture after cross-compiling the package!

📦 If a list of packages is given on the command line, then only those debs with names in this list of packages will be installed.

💡 Note that unlike cvs-buildpackage, the only way to specify the source package name is with the -P option; you cannot simply have it as the last command-line parameter.

🔐 Since installing a package requires root privileges, debi calls debpkg rather than dpkg directly. Thus debi will only be useful if it is either being run as root or debpkg can be run as root. See debpkg(1) for more details.

⚙️ OPTIONS
ℹ️ All current cvs-buildpackage options are silently accepted; however, only the ones listed below have any effect. For more details on all of them, see the cvs-buildpackage(1) manpage.

🏗️ -adebian-architecture, -tGNU-system-type
See dpkg-architecture(1) for a description of these options. They affect the search for the .changes file. They are provided to mimic the behaviour of dpkg-buildpackage when determining the name of the .changes file.

📂 -Mmodule
🗂️ The name of the CVS module.

📦 -Ppackage
🏷️ The name of the package.

🔢 -Vversion
🔖 The version number of the package.

🏷️ -Ttag
🏷️ The CVS tag to use for exporting sources.

🌳 -Rroot directory
📁 Root of the original sources archive.

📁 -Wwork directory
🛠️ The full path name for the cvs-buildpackage working directory.

🔧 -xprefix
🔤 This option provides the CVS default module prefix.

❓ --help, --version
ℹ️ Show help message and version information respectively.

🔗 SEE ALSO

📘 cvs-buildpackage(1)
📘 cvs-debc(1)
📘 cvs-debuild(1)
📘 debi(1)


👤 AUTHOR
✍️ cvs-buildpackage was written by Manoj Srivastava, and the current version of debi was written by Julian Gilbey <jdg AT debian.org>. They have been combined into this program by Julian Gilbey.