<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 25/11/2012 14:55, Chris Wilson a
écrit :<br>
</div>
<blockquote
cite="mid:CAJt9Aa0xZDw384+xEt35Sv=pPazwqm4psQQxQvtL+vXfsF9qXQ@mail.gmail.com"
type="cite">
<div>These can be viewed on the wiki page here: <a
moz-do-not-send="true"
href="https://wiki.ubuntu.com/PaperCuts/MeetingMinutes/22Nov2012#preview">https://wiki.ubuntu.com/PaperCuts/MeetingMinutes/22Nov2012</a></div>
<br>
</blockquote>
<br>
<blockquote
cite="mid:CAJt9Aa0xZDw384+xEt35Sv=pPazwqm4psQQxQvtL+vXfsF9qXQ@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>==== 'One click' setup script for Compiz/Unity ====</div>
<div>If we're going to be targetting Compiz, for paper cut
manifesting in Unity, then it's important for contributors to be
able to test their patches easily, and for that thay have to be
able to build both Compiz and Unity with the minimal of
headaches, something neither of these packages really allows for
at the moment.</div>
<div><br>
</div>
<div>A script should be written, and regularly maintained, that
will allow the user to branch and build both Compiz and Unity
from source, and immediately have it up and running. There are
many unanounced chaned to the build dependencies to Unity so in
order to keep the script upto date, the help of the Unity devs
should be enlisted here.</div>
<div><br>
</div>
<div>In order to make sure it was always working, it needs to be
tested regularly, preferably daily. The best way to do this
would be to use Ubuntu's [[<a moz-do-not-send="true"
href="https://jenkins.qa.ubuntu.com/%7CJenkins">https://jenkins.qa.ubuntu.com/|Jenkins</a>]]
server for automated daily build testing.</div>
</blockquote>
<br>
Hey,<br>
<br>
Do you know that in the coming weeks, we'll have the whole unity
stack (and not restricted to it), being built daily in ubuntu?
Meaning that if you have a fix in unity, you don't surely won't need
to build the latest nux or compiz because it will be in ubuntu :)<br>
<br>
Also, it means that once a papercut is reviewed and landed to trunk,
the day after, it will be in ubuntu, quite motivating, isn't it? :)<br>
<br>
So fixing something will only ask for (for instance, in unity):<br>
- sudo apt-get build-dep unity<br>
- bzr branch lp:unity<br>
- <hack your fix><br>
- bzr bd<br>
-> install the packages, tests<br>
<br>
So, I guess this script is really not needed (nor the machinery to
have it running everyday).<br>
<br>
Also, ensure that all UI/behavior changes are first talked with the
design team (John Lea) so that they are accepted before proposing
the change.<br>
<br>
Thanks a lot for this awesome ongoing effort.<br>
<br>
Cheers,<br>
Didier<br>
</body>
</html>