On Wed, 2008-07-09 at 07:12 -0700, Alan Coopersmith wrote:
>
> Halton Huo wrote:
> > On Wed, 2008-07-09 at 00:20 +1200, Laszlo (Laca) Peter wrote:
> >> Halton,
> >>
> >> Again, a better fix would be to check if Xephyr or Xnest is available
> >> in configure. It should be an upstreamable change.
> > Laca,
> >
> > Xephyr/Xnest is not needed during building time. It need to be in $PATH
> > during run-time. Xephyr is recommenced replacement for Xnest, I'm trying
> > to persuade maintainer to accept this idea.
>
> Then couldn't you at run time try execing Xephyr first, and if that fails,
> try execing Xnest instead? Xephyr is much newer than Xnest, and not found
> on many older systems. (We only have it in S10U4 and later for instance.)
Yes, that is reasonable, will remake the patch.
>
