2 ms·
> 1. The equivalents of "going to the website", forking, adding to local git config, are all skipped for the Debian workflow; it is assumed one has already set
by IronBacon 8y ago
> 1. The equivalents of "going to the website", forking, adding to local git config, are all skipped for the Debian workflow; it is assumed one has already set the project up locally. For a new project, these steps are 100% guaranteed to be more complex for Debian (or any project not on a website with fork-like features).
Naah, you only need to know the URL of the Debian package's .dsc file that you want to patch, and pass it to the dget command, it will download the application tarball, the Debian patches and the dsc file.
You can find the dsc URLs on the Debian packages tracker site: tracker.debian.org
- lucideer 8y agoHow do I get to the Debian packages tracker site? Do I need to open a browser? On a more serious note: you open with "Naah", but then you do go on to describe steps that the author neglected to include in the bullet points. My only point was: the author goes out of their way to make the comparison imbalanced.
- IronBacon 8y agoI was objecting the "Debian workflow is more complex than a forking" part. In reality it's even simpler than what I described (if you don't remove the deb-src lines from your apt source config like I do). If you want to modify a Debian package you only need to use "source" instead of "install" for the package you need, for example "apt source curl" will download the tarball, diff and dsc file for the curl package in the working directory, no browser involved. ^__^; I use the tracker site when I need to build some packages from unstable or experimental, usually recent libraries that I couldn't find on backports.debian.org.