Difference between revisions of "New Build Process"
m (Added a category) |
m (Fixed information about where MakeRelease works and outputs.) |
||
| Line 2: | Line 2: | ||
= Old Way Of Doing Things = | = Old Way Of Doing Things = | ||
| − | At the moment, the builder uses MakeRelease to build all packages. It does so, by copying over the relevant source files into a temporary directory below /var/lmce/out/ named after the package. After that, dpkg-buildpackage is executed, and the resulting deb file ends up in the out directory. | + | At the moment, the builder uses MakeRelease to build all packages. It does so, by copying over the relevant source files into a temporary directory below /var/lmce/out/tmp/ named after the package. After that, dpkg-buildpackage is executed, and the resulting deb file ends up in the out/tmp directory. |
= Goal = | = Goal = | ||
Revision as of 20:41, 2 April 2012
Old Way Of Doing Things
At the moment, the builder uses MakeRelease to build all packages. It does so, by copying over the relevant source files into a temporary directory below /var/lmce/out/tmp/ named after the package. After that, dpkg-buildpackage is executed, and the resulting deb file ends up in the out/tmp directory.
Goal
The goal is, to have the debian directory structure as part of our svn. That way, people can more easily add/change dependencies for existing packages. In addition to easier maintenance, it will allow for REAL debian source packages, that people can use to rebuild packages for other operating systems, as long as they have the needed prerequisites.
Course of action
MakeRelease shall be amended to not delete the created directory after building. The created output shall be expected, and moved into svn.
