| Server IP : 49.231.201.246 / Your IP : 216.73.216.248 Web Server : Apache/2.4.18 (Ubuntu) System : Linux 246 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:56 UTC 2021 x86_64 User : root ( 0) PHP Version : 7.0.33-0ubuntu0.16.04.16 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/dash/ |
Upload File : |
Dash sources for Debian ----------------------- The dash Debian package sources are available through git, and through 'apt-get source dash'. Getting the sources through git should be preferred: # apt-get install git # if not yet done $ git clone http://smarden.org/git/dash.git/ $ cd dash After cloning the repository, you have checked out the debian-sid branch, ready to be used by dpkg-buildpackage, e.g. $ dpkg-buildpackage -i -rfakeroot -uc -us If you want to make changes in the ./debian/ subdirectory, this is the correct branch to work on. After making changes, document them in debian/changelog, and commit through 'git add' and 'git commit', or 'git commit -a', or similar. If you think the changes should be incorporated into the standard Debian package, create the patch[es] through 'git format-patch', and send them to the Debian Bug Tracking System, e.g. $ vi debian/rules $ debchange -pi $ git commit -a $ git format-patch HEAD^ If you want to make changes to the upstream dash sources, first checkout the release+patches branch $ git checkout -b release+patches origin/release+patches The release+patches branch holds patches on top of the current release version that is packaged for Debian/unstable. The current release version is available in the release branch. If you are interested, you can checkout this branch too $ git checkout -b release origin/release When releasing a new Debian package based on a new upstream release, the release branch will be fastforwarded, and the release+patches branch is rewound and rebased onto the new HEAD of the release branch. This is done by, e.g. $ git checkout release $ git merge v0.5.5 $ git checkout release+patches $ git rebase release You generally don't need to do that, but beware that the release+patches branch is rewound occasionally. After checking out the release+patches branch, make the desired changes to the upstream sources, and commit them. To integrate the changes into the Debian package, extract these changes, and change to the debian-sid branch (Note: the file extension for the patches is '.diff', use 'git config --add format.suffix .diff' to make that the default) $ git format-patch release..release+patches $ git checkout debian-sid Now move the extracted patches into the debian/diff/ directory, add a meaningful message to debian/changelog, and commit the changes to the debian-sid branch $ mv ????-*.diff debian/diff/ $ git add debian/diff $ debchange -pi $ git add debian/changelog $ git commit Again, if you think the changes should be incorporated into the standard Debian package, create the patch[es] from the debian-sid branch through 'git format-patch', send them to the Debian Bug Tracking System. There's a mailing list to coordinate work on the dash packages, if you're interested in helping please subscribe to the <debian-package-dash> mailing list by sending an email to <debian-package-dash-subscribe@list.smarden.org>. -- Gerrit Pape <pape@smarden.org> Fri, 04 Jun 2010 00:22:12 +0000