3796
Comment:
|
3803
|
Deletions are marked like this. | Additions are marked like this. |
Line 24: | Line 24: |
||python-ecore ||[http://git.debian.org/?p=pkg-e/proto/python-efl/python-ecore.git;a=summary proto/python-efl/python-ecore.git] ||0.2.1 || Ready || | ||python-ecore ||[http://git.debian.org/?p=pkg-e/proto/python-efl/python-ecore.git;a=summary proto/python-efl/python-ecore.git] ||0.2.1 ||New queue || |
Line 27: | Line 27: |
||python-evas ||[http://git.debian.org/?p=pkg-e/proto/python-efl/python-evas.git;a=summary proto/python-efl/python-evas.git] ||0.2.1 ||Ready || | ||python-evas ||[http://git.debian.org/?p=pkg-e/proto/python-efl/python-evas.git;a=summary proto/python-efl/python-evas.git] ||0.2.1 ||New queue || |
e17 Desktop Environment for the Debian GNU/Linux distribution
e17 is currently maintained by the Debian e17 Maintainer Group.
[http://alioth.debian.org/projects/pkg-e/ Alioth Project Home Page]
[http://lists.alioth.debian.org/mailman/listinfo/pkg-e-devel E17 Maintainers Mailing List]
[https://alioth.debian.org/tracker/?group_id=30943 Alioth BTS]
[http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=pkg-e-devel@lists.alioth.debian.org Debian BTS]
[http://qa.debian.org/developer.php?login=pkg-e-devel@lists.alioth.debian.org QA Page]
[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405860 WNPP: ITP #405860]
- irc.freenode.net #pkg-e
E17 Maintainers < pkg-e-devel@lists.alioth.debian.org >
Packages
GIT Workflow
Suggestion by Jan Lübbe (shoragan)
This is based on madcoder's talk at FOSDEM 2008. It will allow us to do:
git clone git://git.debian.org/git/pkg-e/libs/embryo.git cd embryo git-buildpackage
This will build the current development version in the repository without having any other local setup.
attachment:git-workflow-legend.png
At first we import the upstream tarballs into git and tell git which tarball (in the upstream branch, with upstream/{version} tags) corresponds to which version in upstream's VCS (in the upstream-vcs branch, with upstream-vcs/{version} tags). This will allow us to easily pull fixes from there. After importing three versions our repository looks like this:
attachment:git-workflow-upstream.png
Then we can branch from a upstream/{version} tag and add the debian packaging. When we have a new version in the upstream branch, we simply merge it into the master branch. The tree corresponding to a version uploaded to Debian is tagged debian/{version}.
attachment:git-workflow-debian.png
This is how it looks in gitk:
attachment:git-workflow-gitk.png
The original upstream tarballs are stored as deltas to upstream/{version} in the pristine-tar branch.
Repository
Old: http://bzr.debian.org/pkg-e/
- e17
- libs
- ecore/
- edje/
- eet/
- embryo/
- emotion/
- evas/
- e_dbus/
- apps
- e/
- libs
- e_modules (currently out of date)
- e17