Well, I've seen systems break before when doing this (take an ubuntu package from launchpad), so I'd really rather not.<br>Have seen horrible dependency problems result from it (maybe not immediately, but somewhere down the line).<br>
<br>So yes, I consider it a really bad idea (bad practice?) and I will never ever do this :P<br><br><br><br><div class="gmail_quote">On Tue, Sep 25, 2012 at 1:19 AM, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 09/24/2012 03:46 PM, dreamer wrote:<br>
> On Sun, Sep 23, 2012 at 8:22 PM, Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>>wrote:<br>
><br>
>> launchpad only builds packages for the Ubuntu releases, but you could use<br>
>> one of the Ubuntu packages on Debian if you find an Ubuntu release that is<br>
>> close to your Debian release.<br>
>><br>
> That sounds like a really bad idea. I'd rather use an actual Debian package.<br>
><br>
<br>
</div></div>I'd also rather use the package built against the same Debian release,<br>
but its not a bad idea to try to install a package on your Debian<br>
install when its built on Ubuntu. Worst thing, you'll just have to<br>
uninstall it. Its not going to install other packages from Ubuntu, only<br>
from Debian, unless you've configured it to do differentl.y<br>
<span class="HOEnZb"><font color="#888888"><br>
.hc<br>
</font></span></blockquote></div><br>