public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] re: sys-fs/lvm2 question
Date: Sat, 23 Aug 2014 10:22:50 +0200	[thread overview]
Message-ID: <53F84F5A.7080202@gmail.com> (raw)
In-Reply-To: <53F8480C.2060100@gmail.com>

On 23/08/2014 09:51, Alexander Kapshuk wrote:
> On 08/23/2014 10:31 AM, Samuli Suominen wrote:
>> xfce4-power-manager-1.3.0 and older uses UDisks 1.x for controlling disk
>> spinning, like to reduce it
>>
>> xfce4-power-manager-1.3.1 and higher removed UDisks 1.x dependency and
>> the spindown feature, supposedly it had issues
>> and doesn't work with SSD anyway... anyways, upstream decision to not
>> use udisks anymore
>>
>> so, i recommend upgrading to 1.3.1, adding it to package.keywords if
>> required
>>
>> thanks,
>> samuli
> Thanks for your response.
> 
> I remember being advised on this list against mixing both stable and
> unstable packages as much as possible.
> 
> Does that still hold true? Or would it be OK to pull this one in without
> braking anything unnecessarily?


I think you have a wrong impression. There is actually not much wrong
with mixing stable and unstable as long as you do it sensibly.

What you shouldn't do is to wantonly mix packages in @stable and other
basic libs and still expect it to work. Stable gcc and unstable glibc
with jpeg, zlib and openssl all mixed and matched any old way is certain
to show inconsistencies (as you will be the only person who has ever
tested that combination).

What is being proposed here is that you take one userland package
(xfce4-power-manager) and upgrade it to the new version. It's highly
unlikely to break anything and I can tell that just by looking at it's
purpose and where it fits in the stack. It will either work or not, and
the list of things that might link to it are a rather small list indeed.

So just give it a spin, you can always revert if it's incompatible with
everything else you have.

The answer to the last question you pose is correctly "mu" as no-one can
possibly answer it properly. The best we can do for you is paint the big
picture and ask you to try then report back if it works, as I have done
above.



-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2014-08-23  8:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 18:56 [gentoo-user] re: sys-fs/lvm2 question Alexander Kapshuk
2014-08-22 19:36 ` Canek Peláez Valdés
2014-08-23  6:47   ` Alexander Kapshuk
2014-08-23  6:53     ` Canek Peláez Valdés
2014-08-23  7:17       ` Alexander Kapshuk
2014-08-23  7:31       ` Samuli Suominen
2014-08-23  7:51         ` Alexander Kapshuk
2014-08-23  8:22           ` Alan McKinnon [this message]
2014-08-23  8:29             ` Alexander Kapshuk
2014-08-26 17:13               ` Alexander Kapshuk
2014-08-23  7:48       ` Alexander Kapshuk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53F84F5A.7080202@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox