udev-151 is now in the tree - this ebuild is masked and has **not been
tested** (it is there for further testing and development.) If you
have a package.unmask entry for udev, make sure it does not apply to
the udev-151 unless you have a LiveCD handy and want to commit to
testing this.
-Daniel
--
You received this message because you are subscribed to the Google Groups "Funtoo" group.
To post to this group, send email to funto...@googlegroups.com.
To unsubscribe from this group, send email to funtoo-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/funtoo-dev?hl=en.
On 12 avr, 21:13, Jean-Francis Roy <jeanfrancis...@gmail.com> wrote:
> Thanks Daniel! Unmasking udev-151 will help gnome-2.30 users not to run into
> missing dependency problems. I just installed it and let you know if I run
> into any problem.
>
> ~JF
>
> On Mon, Apr 12, 2010 at 1:25 PM, Daniel Robbins <drobb...@funtoo.org> wrote:
> > Hi All,
>
> > udev-151 is now in the tree - this ebuild is masked and has **not been
> > tested** (it is there for further testing and development.) If you
> > have a package.unmask entry for udev, make sure it does not apply to
> > the udev-151 unless you have a LiveCD handy and want to commit to
> > testing this.
>
> > -Daniel
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Funtoo" group.
> > To post to this group, send email to funto...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > funtoo-dev+...@googlegroups.com<funtoo-dev%2Bunsu...@googlegroups.com>
Do you know of any considerations before testing this version of udev?
It won't be the first time that the upgrade ends up breaking
something.
Regards.
> --
> You received this message because you are subscribed to the Google Groups "Funtoo" group.
> To post to this group, send email to funto...@googlegroups.com.
> To unsubscribe from this group, send email to funtoo-dev+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/funtoo-dev?hl=en.
>
>
--
Ioannis Aslanidis
http://www.deathwing00.org
<deathwing00[at]gentoo.org> 0x47F370A0
Regarding any problems with the ebuild, I don't know as it needs
testing. No obvious failures.
If you are talking about things breaking due to new udev code, I am
not sure either. If anyone has any info, post here.
It does at least sound like some people are using it successfully? Is
this the case?
-Daniel
d2_racing
On 13 avr, 13:23, Jean-Francis Roy <jeanfrancis...@gmail.com> wrote:
> Same here, working out of the box.
>
> ~JF
>
> On Tue, Apr 13, 2010 at 1:16 PM, shayes <nekoj...@gmail.com> wrote:
> > So far, nothing bad happens
>
> > > Regarding any problems with the ebuild, I don't know as it needs
> > > testing. No obvious failures.
>
> > > If you are talking about things breaking due to new udev code, I am
> > > not sure either. If anyone has any info, post here.
>
> > > It does at least sound like some people are using it successfully? Is
> > > this the case?
>
> > > -Daniel
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Funtoo" group.
> > To post to this group, send email to funto...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > funtoo-dev+...@googlegroups.com<funtoo-dev%2Bunsu...@googlegroups.com>
On 13 avr, 19:14, Daniel Robbins <drobb...@funtoo.org> wrote:
> On Tue, Apr 13, 2010 at 11:09 AM, Ioannis Aslanidis
>
Bob
Daniel Robbins wrote :
> I have been using it for about a month (imported in my local overlay from
> gentoo tree), no problem so far.
Note that the funtoo ebuild is quite different from the gentoo ebuild for udev.
-Daniel
On Apr 13, 2010, at 11:59 PM, Daniel Robbins <drob...@funtoo.org>
wrote:
> On Apr 13, 2010, at 12:34 PM, Boby Jacky wrote:
--
Victor Leonel Orozco (tuxtor) - http://tuxtor.shekalug.org
I'm also on ~amd64 and it's working well.
--
Victor Leonel Orozco (tuxtor) - http://tuxtor.shekalug.org
On Apr 14, 12:34 pm, Guy Fontaine <arami...@gmail.com> wrote:
> udev-151 has been bumped (if I can say so) to unstable branch of Gentoo
> Portage tree. It was available at time I eix-sync'ed my Gentoo box. It was
> so for xorg-server 1.8.0 at the same time.
>
> I added extras to USE flags of /etc/make.conf and performed the update
> (emerge --update --newuse --deep @world. All emerged successfully. There was
> a note to modify /etc/conf.d/xdm by adding NEEDS_HALD set either to no or
> yes or auto as the case may be. I did not modify that file.
>
> I only recompiled xf86 drivers (input-evdev, input-mouse, input-keyboard,
> input-synaptics, video-intel and video-vesa). Restarting the system worked
> fine.
>
> I'm now running my Gentoo unstable (amd64) box with xorg-server-1.8.0.
>
> Guy Fontaine (aramis_qc)
>
> 2010/4/14 Víctor Orozco <caballerodelme...@gmail.com>
>
>
>
> > I'm also on ~amd64 and it's working well.
>
> > --
> > Victor Leonel Orozco (tuxtor) -http://tuxtor.shekalug.org
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Funtoo" group.
> > To post to this group, send email to funto...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > funtoo-dev+...@googlegroups.com<funtoo-dev%2Bunsubscribe@googlegrou ps.com>
Does this mean hal can be unmerged at this point?
If you've got no other packages that depend on it, I don't see any
problems in unmerging hal
equery d sys-apps/hal
If there's a package in need of hal (no USE-flag, hardcoded dep), then
you shouldn't unmerge it right now and wait, what future versions will
bring.
If it's just something like vlc, disable the USE-flag and reemerge the
package.
I'm running both my laptop (xmonad) and my media-server (icewm)
without hal for a few weeks now and didn't experience any problems so
far.
I never liked the idea of something being automounted on one of my
systems, so I never needed hal for that sort of thing (only had it
installed because it was decided by the xorg-devs to outsource those
input device to one package [<3 evdev <3])
On Apr 14, 9:34 pm, Guy Fontaine <arami...@gmail.com> wrote:
> There was a note to modify /etc/conf.d/xdm by adding NEEDS_HALD set either
> to no or > yes or auto as the case may be. I did not modify that file.
>
> I only recompiled xf86 drivers (input-evdev, input-mouse, input-keyboard,
> input-synaptics, video-intel and video-vesa). Restarting the system worked
> fine.
NEEDS_HALD is dropped in x11-apps/xinit-1.2.1-r1
(Besides: xf86-input-keyboard and xf86-input-mouse are not needed,
when you're using evdev ;o)
NEEDS_HALD is dropped in x11-apps/xinit-1.2.1-r1
(Besides: xf86-input-keyboard and xf86-input-mouse are not needed,
when you're using evdev ;o)