[09:45] <MCR_> smspillaz, hi :)
[09:45] <MCR_> smspillaz, the best way to test core changes is via PPA
[09:46] <MCR_> it is not so easy (at least for me) to replace my local installation of Compiz/Unity with trunk, because I do not run default Ubuntu
[09:46] <MCR_> additional lenses for example make a self-compiled Unity crash on you once you try to open the Dash
[09:47] <MCR_> and I do not even want to start talking about all the self-compiled Compiz plugins and the special CCSM settings
[09:48] <MCR_> so ofc. I can test core trunk, but not in the *real* conditions
[09:48] <MCR_> but if you have any additional magic scripts for me they are wellkommen
[09:50] <MCR_> I have written some for auto-updating/compiling/installing Unity/nux/libunity&co, but those are pretty standard...
[10:51] <smspillaz> MCR_: so, you don't need to replace your installation
[10:51] <smspillaz> MCR_: what I'm asking is if you can install the branch *locally* along with unity (eg to ~/apps/ as the prefix)
[10:51] <smspillaz> and then test that
[10:52] <smspillaz> I don't see how that creates problems for your setup
[10:59] <MCR_> smspillaz, try to install additional lenses and scopes and you'll notice ;)
[11:00] <smspillaz> MCR_: I don't see why that has anything to do with testing the wall plugin
[11:00] <MCR_> that is true
[11:00] <smspillaz> the whole point is that you create a separate installation so that you can test things
[11:00] <MCR_> but it is not *really* needed in this case
[11:01] <MCR_> you say it works
[11:01] <smspillaz> MCR_: well, did you want to test my changes or not?
[11:01] <MCR_> code looks good
[11:01] <smspillaz> its currently blocked on someone else testing them ... so ........
[11:01] <MCR_> I'll test it once it lands in trunk
[11:01] <smspillaz> MCR_: have a look to see if you can test it within the next three days
[11:01] <smspillaz> theres no rush
[11:01] <MCR_> what is the problem ?
[11:01] <smspillaz> *shrug* just some testing would be good
[11:02] <MCR_> if you tested it...
[11:02] <smspillaz> ... from someone else ...
[11:02] <MCR_> and I promise to test it once it lands
[11:02] <MCR_> with all the goodies I have enabled
[11:02] <smspillaz> MCR_: well, in any case, you're going to be in a position where you'll need to test core changes
[11:02] <MCR_> I will immediately report any problems
[11:02] <smspillaz> I suggest that you look into building a separate installation
[11:02] <MCR_> I know how to do it, do not worry
[11:03] <smspillaz> ... then do it?
[11:03] <MCR_> I just do not *like* to do it, when it is not strictly necessary
[11:03] <MCR_> I have to go in the virtual console
[11:03] <smspillaz> no you dont
[11:03] <MCR_> oh
[11:04] <smspillaz> PATH=/path/to/prefix/ compiz --replace ccp &
[11:04] <smspillaz> done.
[11:04] <smspillaz> in a gnome-terminal or whatever
[11:04] <MCR_> whot ?
[11:04] <smspillaz> MCR_: you don't need to launch from a vt
[11:05] <MCR_> I always used Daniel's version: https://answers.launchpad.net/compiz/+question/203490
[11:05] <MCR_> but then for example my CCSM settings get all messed up
[11:05] <MCR_> Compiz runs without Unity and so on
[11:05] <smspillaz> so that's one way of doing it
[11:05] <smspillaz> "ccp" loads the compizconfig plugin which will pull in all your settings
[11:06] <smspillaz> including plugin lists
[11:06] <MCR_> so to test in a *real* environment a lot is needed and as I said if you have Unity lenses, scopes which are not in the unity source you are f*cked also
[11:06] <smspillaz> MCR_: It will be quite rare when you run into a situation where you need the lenses installed for local testing
[11:07] <MCR_> it is enough to try to open the dash to make everything crash then
[11:07] <smspillaz> in any case, you can build packages of compiz pretty much instantly
[11:07] <MCR_> because unity gets confused
[11:07] <smspillaz> just debuild in the compiz director
[11:07] <smspillaz> it will create deb packages
[11:07] <MCR_> debuild
[11:07] <smspillaz> anyways, I need to go to dinner, but look into getting that local installation working for doing local tests
[11:07] <MCR_> that is all that is needed to build all packages ?
[11:07] <smspillaz> it will pay off in the long term, trust me
[11:08] <smspillaz> MCR_: sudo apt-get build-dep compiz unity
[11:08] <smspillaz> the good thing about inline packaging is that you can literally just debuild in the source dir and it will make a package for you
[11:08] <smspillaz> which you can install with dpkg
[11:08] <smspillaz> anyways, gotta run
[11:08] <MCR_> c ya