On Sun, 15 Dec 2002, Guido Guenther wrote:
> Thats great! Did you bother to check what x.org did already about IPv6?
> As far as I know they plan to put it into their next release and XFree86
> syncs with these releases fairly quickly, so we might end up with two
> different implementations.
> Reg
On Sun, Dec 15, 2002 at 08:20:30AM +0100, Fabio Massimo Di Nitto wrote:
> No there is no risk at all. Once X.org will release IPv6 upstream this
> patch set will be obsolete and can be removed. I do not see much
> more than: X11R6.7 will include IPv6. and this let me think they will
> more or less
On Sun, 15 Dec 2002, Guido Guenther wrote:
> On Sun, Dec 15, 2002 at 08:20:30AM +0100, Fabio Massimo Di Nitto wrote:
> > No there is no risk at all. Once X.org will release IPv6 upstream this
> > patch set will be obsolete and can be removed. I do not see much
> > more than: X11R6.7 will include
Is there a big reason why lndir is not used instead of cp in the build
rules?
For reasons of disk space alone something along the lines of:
mkdir $(SOURCE_TREE)
lndir ../../$(SOURCE_TREE)-real $(SOURCE_TREE)/ ifndef
NOT_BUILDING_X_SERVER
# create source tree for static, d
On Son, 2002-12-15 at 16:28, Zephaniah E. Hull wrote:
> Is there a big reason why lndir is not used instead of cp in the build
> rules?
>
> For reasons of disk space alone something along the lines of:
>
> mkdir $(SOURCE_TREE)
> lndir ../../$(SOURCE_TREE)-real $(SOURCE_TREE)/ ifnd
Package: xfree86-common
Version: 4.2.1-3
Severity: normal
I don't know what package is responsible of that, but I find that in X I
have two clipboard.
If I do a copy in kmail, the gnome clipboard is void, but the thing I
copied is disponible and I can paste it (in gnome) with the middle mouse
I no longer run the crashing vesa driver, but have instead a manually
kludged up installation that works with i830 stuff. Unfortunately, the
machine has stopped booting from anything except the hard disk, which
means I'm not going to play with it in any way that may jeopardize its
bootability until
On Sun, Dec 15, 2002 at 05:56:16PM +0100, Michel D?nzer wrote:
> On Son, 2002-12-15 at 16:28, Zephaniah E. Hull wrote:
> > Is there a big reason why lndir is not used instead of cp in the build
> > rules?
> >
> > For reasons of disk space alone something along the lines of:
> >
> > mkdir
One Sun engineer claimed on the XFree86 lists that the IPv6
implementation required a minor protocol change. Of course, this may
have been mere bragging (of the ``look, we've done some really hard
work''), or else an indication of how they like to do complicated
things when it's not needed. (Yes,
FMDN> I was not aware of other implementations when i started merging and
FMDN> working on this one (talking about Sun and INRIA). Are they publically
FMDN> available?? any URL??
Fabio,
The INRIA implementation is but a vague memory. I don't think that
Sun's implementation is available to the ge
> However, it does seem to imply that there is a risk of non-inter-
> operable X11 implementations if your patches get in. I'd be very
> surprised if upstream accepted an IPv6 implementation (from you or
> from somewhere else) before they see Sun's code.
from a very fast investigation X.org only
On Sunday 15 December 2002 02:24 pm, Juliusz Chroboczek wrote:
> I would suggest that you should wait until Sun publish their code, and
> if then you think that yours is better (which it might very well be)
> try to get upstream to use yours.
Don't wait to publish your code upstream. If you wait, y
The paths are better handled by defoma :
dir "/usr/share/fonts/truetype/freefont"
dir "/usr/share/fonts/truetype"
can both be replaced by
dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
I also have the following line :
dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
HTH,
--
Rémi L
Processing commands for [EMAIL PROTECTED]:
> reassign 173229 xserver-xfree86
Bug#173229:
Bug reassigned from package `debian/xserver' to `xserver-xfree86'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
On Sun, Dec 15, 2002 at 08:20:30AM +0100, Fabio Massimo Di Nitto wrote:
> No there is no risk at all. Once X.org will release IPv6 upstream this
> patch set will be obsolete and can be removed. I do not see much
> more than: X11R6.7 will include IPv6. and this let me think they will
> more or less
On Sun, 15 Dec 2002, Guido Guenther wrote:
> On Sun, Dec 15, 2002 at 08:20:30AM +0100, Fabio Massimo Di Nitto wrote:
> > No there is no risk at all. Once X.org will release IPv6 upstream this
> > patch set will be obsolete and can be removed. I do not see much
> > more than: X11R6.7 will include
Is there a big reason why lndir is not used instead of cp in the build
rules?
For reasons of disk space alone something along the lines of:
mkdir $(SOURCE_TREE)
lndir ../../$(SOURCE_TREE)-real $(SOURCE_TREE)/ ifndef NOT_BUILDING_X_SERVER
# create source tree for static, de
On Son, 2002-12-15 at 16:28, Zephaniah E. Hull wrote:
> Is there a big reason why lndir is not used instead of cp in the build
> rules?
>
> For reasons of disk space alone something along the lines of:
>
> mkdir $(SOURCE_TREE)
> lndir ../../$(SOURCE_TREE)-real $(SOURCE_TREE)/ ifnd
Package: xfree86-common
Version: 4.2.1-3
Severity: normal
I don't know what package is responsible of that, but I find that in X I
have two clipboard.
If I do a copy in kmail, the gnome clipboard is void, but the thing I
copied is disponible and I can paste it (in gnome) with the middle mouse
I no longer run the crashing vesa driver, but have instead a manually
kludged up installation that works with i830 stuff. Unfortunately, the
machine has stopped booting from anything except the hard disk, which
means I'm not going to play with it in any way that may jeopardize its
bootability until
On Sun, Dec 15, 2002 at 05:56:16PM +0100, Michel D?nzer wrote:
> On Son, 2002-12-15 at 16:28, Zephaniah E. Hull wrote:
> > Is there a big reason why lndir is not used instead of cp in the build
> > rules?
> >
> > For reasons of disk space alone something along the lines of:
> >
> > mkdir
One Sun engineer claimed on the XFree86 lists that the IPv6
implementation required a minor protocol change. Of course, this may
have been mere bragging (of the ``look, we've done some really hard
work''), or else an indication of how they like to do complicated
things when it's not needed. (Yes,
FMDN> I was not aware of other implementations when i started merging and
FMDN> working on this one (talking about Sun and INRIA). Are they publically
FMDN> available?? any URL??
Fabio,
The INRIA implementation is but a vague memory. I don't think that
Sun's implementation is available to the ge
> However, it does seem to imply that there is a risk of non-inter-
> operable X11 implementations if your patches get in. I'd be very
> surprised if upstream accepted an IPv6 implementation (from you or
> from somewhere else) before they see Sun's code.
from a very fast investigation X.org only
On Sunday 15 December 2002 02:24 pm, Juliusz Chroboczek wrote:
> I would suggest that you should wait until Sun publish their code, and
> if then you think that yours is better (which it might very well be)
> try to get upstream to use yours.
Don't wait to publish your code upstream. If you wait, y
The paths are better handled by defoma :
dir "/usr/share/fonts/truetype/freefont"
dir "/usr/share/fonts/truetype"
can both be replaced by
dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
I also have the following line :
dir "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
HTH,
--
Rémi L
Processing commands for [EMAIL PROTECTED]:
> reassign 173229 xserver-xfree86
Bug#173229:
Bug reassigned from package `debian/xserver' to `xserver-xfree86'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
A while ago (maybe about a month), after I rebooted my computer I could no
longer get a GUI. It would flicker once or twice, pop to the attempting to
fix the XFree86 configuration prompt (asking the root password), followed
by displaying a cruder graphical screen showing a picture of a computer, a
28 matches
Mail list logo
