Merge lp:~jml/pkgme/rules-extra-targets into lp:pkgme
Status: | Merged |
---|---|
Approved by: | James Westby |
Approved revision: | 118 |
Merged at revision: | 119 |
Proposed branch: | lp:~jml/pkgme/rules-extra-targets |
Merge into: | lp:pkgme |
Diff against target: |
80 lines (+26/-0) 4 files modified
pkgme/info_elements.py (+6/-0) pkgme/package_files.py (+2/-0) pkgme/templates/rules (+3/-0) pkgme/tests/test_package_files.py (+15/-0) |
To merge this branch: | bzr merge lp:~jml/pkgme/rules-extra-targets |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
James Westby | Approve | ||
Review via email: mp+113951@code.launchpad.net |
Commit message
Allow extra targets to be specified in rules.
Description of the change
This is a very simplistic attempt at adding support for customizing the
'rules' file generated by pkgme. It is my own poor attempt at accommodating
directhex's needs, described below in a slightly edited version of their own
words.
For my part, I'm worried that this is too unstructured, and have vague fears
that it will allow pkgme to become yet another broken packaging system. As
such, I defer to the expert while trying to unblock directhex in their work.
...
directhex has been working on adding support to pkgme for handling building
of mono projects with xbuild, a command-line tool which can build visual
studio project and solution files (which monodevelop uses as its native
project format).
It should give far greater coverage than relying on mono developers to create
automake projects.
A mono source tree can contain multiple solution (.sln) and project (.csproj)
files, without any guarantees as to which is the "correct" one to build.
This is especially common for multi-platform projects where they might ship a
different .sln with different defaults for windows, osx, linux, silverlight,
etc
The usual strategy is to specify which project to build in 'rules', much like
passing a -f value to "make" which is typically done by overriding
dh_auto_build and dh_auto_clean. However, pkgme doesn't seem to have any
support for overrides, since the template format assumes a pristine dh $@ is
enough for anybody in all situations.
...
Thanks,
jml
Let's give this a go and see what happens...
Thanks,
James