Re: XF86Config-4 not generated

2001-04-13 Thread Ilya Martynov


CS Hi,
CS since I did not find an /etc/X11/XF86Config-4 file after upgrading to X
CS Windows (4.0.2-7), I did

CS dpkg-reconfigure xserver-free86

CS answered all the questions, and expected that a new XF86Config-4 would be
CS produced.  But still no, I could not find any file of that name on my whole
CS system...

CS (I know that I can just run xf86config myself.  I'm just wondering if that
CS is a bug in Debian's config scripts...)

I just want to say: I saw it too. IMHO it is a bug.

-- 
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Ilya Martynov (http://martynov.org/)|
| GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80  E4AE BE1A 53EB 323B DEE6 |
| AGAVA Software Company (http://www.agava.com/)  |
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: XF86Config-4 not generated

2001-04-13 Thread Dave Swegen

I found this problem too. What I found is that I had to run dexconf
after the configuration was done. Mind you, the config it generated was
broken with regards to the pointer section...

Cheers
Dave

On Fri, Apr 13, 2001 at 01:07:30PM +0400, Ilya Martynov wrote:
 
 CS Hi,
 CS since I did not find an /etc/X11/XF86Config-4 file after upgrading to X
 CS Windows (4.0.2-7), I did
 
 CS dpkg-reconfigure xserver-free86
 
 CS answered all the questions, and expected that a new XF86Config-4 would be
 CS produced.  But still no, I could not find any file of that name on my whole
 CS system...
 
 CS (I know that I can just run xf86config myself.  I'm just wondering if that
 CS is a bug in Debian's config scripts...)
 
 I just want to say: I saw it too. IMHO it is a bug.
 
 -- 
  -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 | Ilya Martynov (http://martynov.org/)|
 | GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80  E4AE BE1A 53EB 323B DEE6 |
 | AGAVA Software Company (http://www.agava.com/)  |
  -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
 
 --  
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
 
 


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: DRI fails to work with no errors?

2001-04-13 Thread Michel Dänzer

Benjamin Redelings I wrote:
 
 Hi, according to /proc/pci, I have a "ATI Technologies Inc 3D Rage Pro
 AGP 1X/2X".
 
 I compiled agp and the r128 DRI driver for kernel 2.4.3-ac5.

Your chip isn't a Rage128. There is only rudimentary support for the mach64
family in a branch of the DRI CVS yet.


-- 
Earthling Michel Dnzer (MrCooper)\   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \XFree86 and DRI project member


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: XFree 4.0.3 debs

2001-04-13 Thread Waldemar Brodkorb

Hallo Charl,

* Charl schrieb:

 On Wed, Apr 11, 2001 at 07:02:30PM -0500, Branden Robinson wrote:
  On Wed, Apr 11, 2001 at 04:22:38PM +0200, Waldemar Brodkorb wrote:
   Why libXv.so is not integrated in the new pre-debs from
   Branden Robinson's site?
  
  Because the upstream build process does not compile a shared version.  Xv
  is at present available only as a static library.
  
   It is needed by applications like xine to view
   VCD or DVD in fullscreenmode.
  
  Yes, and they can link it in statically.
  
 
 Alternatively, you could do the following (as root, in /usr/X11R6/lib):
 ld --whole-archive -shared -o libXxf86dga.so libXxf86dga.a
 ld --whole-archive -shared -o libXv.so libXv.a
 
 This tends to do the trick at least for livid (the last time I checked).

Yes, thanks I know this, but why I have to create this on every
machine and then it is not integrated in the package-database,
next upgrade to xfree 4.1 and I will have trouble, when I forgotten
it. After an email to SuSE ([EMAIL PROTECTED]) they have included
this shared version's of libraries in their XFree-packages.

cya
Waldemar

-- 
* A good website for linuxsoftware:|  (o_  *
*   http://www.freshmeat.net   |  //\  *
*   Linux rulez!;-)|  V_/_ *
* GnuPG-Key: 0xBE21BD90 | Tux: #155220 | ICQ: 64035650 *


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Xv client library: shared version?

2001-04-13 Thread Juliusz Chroboczek

Dear Mark,

There has been some discussion recently on the Debian list devoted to
maintaining X (see CC) about the lack of a shared version of the Xv
library.  There would appear to be an opinion that shared versions of
the libraries should be included.

Any chance you could drop a note to the list about the rationale for
not including the shared library in the default XFree86 build, and
whether you think there may be any issues with including such a
library in the Debian version?

Thanks,

Juliusz


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: XFree 4.0.3 debs

2001-04-13 Thread Branden Robinson

On Fri, Apr 13, 2001 at 07:11:49PM +0200, Waldemar Brodkorb wrote:
 * Branden wrote:
 
  On Wed, Apr 11, 2001 at 04:22:38PM +0200, Waldemar Brodkorb wrote:
   Why libXv.so is not integrated in the new pre-debs from
   Branden Robinson's site?
  
  Because the upstream build process does not compile a shared version.  Xv
  is at present available only as a static library.
 
 Is this the only reason? 
 You could put this in host.def :
 #define SharedLibXxf86dga   YES
 #define SharedLibXv YES 

I could (actually, the correct place is linux.cf, inside #if
LinuxDistribution == LinuxDebian), but I won't.  Not without a better
reason than you're giving me.

To understand why, I suggest reviewing the package descriptions of xlibs
and xlibs-dev.

I don't deviate from upstream practice gratuitously.

-- 
G. Branden Robinson |
Debian GNU/Linux|"Bother," said Pooh, as he was
[EMAIL PROTECTED]  |assimilated by the Borg.
http://www.debian.org/~branden/ |

 PGP signature


Re: XF86Config-4 not generated

2001-04-13 Thread Branden Robinson

On Fri, Apr 13, 2001 at 01:57:52PM +0100, Dave Swegen wrote:
 I found this problem too. What I found is that I had to run dexconf
 after the configuration was done. Mind you, the config it generated was
 broken with regards to the pointer section...
 
 Cheers
   Dave
 
 On Fri, Apr 13, 2001 at 01:07:30PM +0400, Ilya Martynov wrote:
  
  CS Hi,
  CS since I did not find an /etc/X11/XF86Config-4 file after upgrading to X
  CS Windows (4.0.2-7), I did
  
  CS dpkg-reconfigure xserver-free86
  
  CS answered all the questions, and expected that a new XF86Config-4 would be
  CS produced.  But still no, I could not find any file of that name on my whole
  CS system...
  
  CS (I know that I can just run xf86config myself.  I'm just wondering if that
  CS is a bug in Debian's config scripts...)
  
  I just want to say: I saw it too. IMHO it is a bug.

You guys will find that these problems is fixed in 4.0.2-13...

-- 
G. Branden Robinson |   No math genius, eh?  Then perhaps you
Debian GNU/Linux|   could explain to me where you got
[EMAIL PROTECTED]  |   these...
http://www.debian.org/~branden/ | PENROSE TILES!

 PGP signature


FreeType2 library built from xfree86_4.0.3.deb's source

2001-04-13 Thread ISHIKAWA Mutsumi


 I've checked and rebuilt Branden's test release
xfree86_4.0.3-0pre1v2.deb. And I found a minor problem.

 XFree86 4.0.3 includes FreeType2 library and it will be built
When defined `HasFreetype2 NO'. The default setting is
`HasFreetype2 NO' and test release package does not change the
setting. 

 Building FreeType2 is not needed because Debian has the FreeType2
library (libfreetype6 and libfreetype6-dev).

 So please add `#define HasFreetype2 YES' line in config/cf/linux.cf
(perhaps it is need to modify debian/patches/005_linux_config.diff to
add it).

Tnanks,
--
ISHIKAWA Mutsumi
 [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]




--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: FreeType2 library built from xfree86_4.0.3.deb's source

2001-04-13 Thread Branden Robinson

On Sat, Apr 14, 2001 at 03:21:01AM +0900, ISHIKAWA Mutsumi wrote:
  I've checked and rebuilt Branden's test release
 xfree86_4.0.3-0pre1v2.deb. And I found a minor problem.
 
  XFree86 4.0.3 includes FreeType2 library and it will be built
 When defined `HasFreetype2 NO'. The default setting is
 `HasFreetype2 NO' and test release package does not change the
 setting. 
 
  Building FreeType2 is not needed because Debian has the FreeType2
 library (libfreetype6 and libfreetype6-dev).
 
  So please add `#define HasFreetype2 YES' line in config/cf/linux.cf
 (perhaps it is need to modify debian/patches/005_linux_config.diff to
 add it).

Thanks for pointing this out, Ishikawa-san[1].  I'll make this change right
away, so that it will go into 4.0.3-1.

[1] I hope I got the honorific correct.

-- 
G. Branden Robinson |Murphy's Guide to Science:
Debian GNU/Linux|If it's green or squirms, it's biology.
[EMAIL PROTECTED]  |If it stinks, it's chemistry.
http://www.debian.org/~branden/ |If it doesn't work, it's physics.

 PGP signature


Re: Xv client library: shared version?

2001-04-13 Thread Mark Vojkovich

On 13 Apr 2001, Juliusz Chroboczek wrote:

 Dear Mark,
 
 There has been some discussion recently on the Debian list devoted to
 maintaining X (see CC) about the lack of a shared version of the Xv
 library.  There would appear to be an opinion that shared versions of
 the libraries should be included.
 
 Any chance you could drop a note to the list about the rationale for
 not including the shared library in the default XFree86 build, and
 whether you think there may be any issues with including such a
 library in the Debian version?
 

  It's not an X-consortium standard, or even a de-facto standard.
If you have an app that links against Xv, it won't even start
unless you have the libraries on your machine.  That would prohibit
using that app with anything other than an XFree86 4.x installation. 

   Say you had an app that wanted to use Xv if available, and do
its own software scaling/color conversion otherwise so it would
work on XiG's server or with 3.3.x.  If you called XvQueryExtension
to find if the extension was available your app will not run.
Debian can include a shared library if they want, but applications
wanting to optionally use Xv would be wise to compile with the static 
version.


Mark.


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Xv client library: shared version?

2001-04-13 Thread Branden Robinson

On Fri, Apr 13, 2001 at 10:53:54AM -0700, Mark Vojkovich wrote:
   It's not an X-consortium standard, or even a de-facto standard.
 If you have an app that links against Xv, it won't even start
 unless you have the libraries on your machine.  That would prohibit
 using that app with anything other than an XFree86 4.x installation. 
 
Say you had an app that wanted to use Xv if available, and do
 its own software scaling/color conversion otherwise so it would
 work on XiG's server or with 3.3.x.  If you called XvQueryExtension
 to find if the extension was available your app will not run.
 Debian can include a shared library if they want, but applications
 wanting to optionally use Xv would be wise to compile with the static 
 version.

Good enough reasoning for me.  I've actually been arguing against shipping
a shared version in Debian's packages until the XFree86 build process does
so, but some of my users are harassing me to do otherwise.

Thanks for the explanation, Mark.

-- 
G. Branden Robinson |You live and learn.
Debian GNU/Linux|Or you don't live long.
[EMAIL PROTECTED]  |-- Robert Heinlein
http://www.debian.org/~branden/ |

 PGP signature


Re: XF86Config-4 not generated

2001-04-13 Thread Ilya Martynov

CS Hi,
CS since I did not find an /etc/X11/XF86Config-4 file after upgrading to X
CS Windows (4.0.2-7), I did

CS dpkg-reconfigure xserver-free86

CS answered all the questions, and expected that a new XF86Config-4 would be
CS produced.  But still no, I could not find any file of that name on my whole
CS system...

CS (I know that I can just run xf86config myself.  I'm just wondering if that
CS is a bug in Debian's config scripts...)

I just want to say: I saw it too. IMHO it is a bug.

-- 
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Ilya Martynov (http://martynov.org/)|
| GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80  E4AE BE1A 53EB 323B DEE6 |
| AGAVA Software Company (http://www.agava.com/)  |
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



Re: XF86Config-4 not generated

2001-04-13 Thread Dave Swegen
I found this problem too. What I found is that I had to run dexconf
after the configuration was done. Mind you, the config it generated was
broken with regards to the pointer section...

Cheers
Dave

On Fri, Apr 13, 2001 at 01:07:30PM +0400, Ilya Martynov wrote:
 
 CS Hi,
 CS since I did not find an /etc/X11/XF86Config-4 file after upgrading to X
 CS Windows (4.0.2-7), I did
 
 CS dpkg-reconfigure xserver-free86
 
 CS answered all the questions, and expected that a new XF86Config-4 would be
 CS produced.  But still no, I could not find any file of that name on my 
 whole
 CS system...
 
 CS (I know that I can just run xf86config myself.  I'm just wondering if that
 CS is a bug in Debian's config scripts...)
 
 I just want to say: I saw it too. IMHO it is a bug.
 
 -- 
  -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 | Ilya Martynov (http://martynov.org/)|
 | GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80  E4AE BE1A 53EB 323B DEE6 |
 | AGAVA Software Company (http://www.agava.com/)  |
  -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
 
 --  
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 



Re: DRI fails to work with no errors?

2001-04-13 Thread Michel Dänzer
Benjamin Redelings I wrote:
 
 Hi, according to /proc/pci, I have a ATI Technologies Inc 3D Rage Pro
 AGP 1X/2X.
 
 I compiled agp and the r128 DRI driver for kernel 2.4.3-ac5.

Your chip isn't a Rage128. There is only rudimentary support for the mach64
family in a branch of the DRI CVS yet.


-- 
Earthling Michel Dänzer (MrCooper)\   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \XFree86 and DRI project member



Re: XFree 4.0.3 debs

2001-04-13 Thread Waldemar Brodkorb
Hello Branden,

* Branden wrote:

 On Wed, Apr 11, 2001 at 04:22:38PM +0200, Waldemar Brodkorb wrote:
  Why libXv.so is not integrated in the new pre-debs from
  Branden Robinson's site?
 
 Because the upstream build process does not compile a shared version.  Xv
 is at present available only as a static library.

Is this the only reason? 
You could put this in host.def :
#define SharedLibXxf86dga   YES
#define SharedLibXv YES 
 
  It is needed by applications like xine to view
  VCD or DVD in fullscreenmode.
 
 Yes, and they can link it in statically.

But I think shared libraries are a good thing or I have
misunderstand something. Sharing code / same functions 
saves memory. 

joke
I don't want to have another soffice.bin.
/joke

bye
Waldemar

-- 
* A good website for linuxsoftware:|  (o_  *
*   http://www.freshmeat.net   |  //\  *
*   Linux rulez!;-)|  V_/_ *
* GnuPG-Key: 0xBE21BD90 | Tux: #155220 | ICQ: 64035650 *



Re: XFree 4.0.3 debs

2001-04-13 Thread Waldemar Brodkorb
Hallo Charl,

* Charl schrieb:

 On Wed, Apr 11, 2001 at 07:02:30PM -0500, Branden Robinson wrote:
  On Wed, Apr 11, 2001 at 04:22:38PM +0200, Waldemar Brodkorb wrote:
   Why libXv.so is not integrated in the new pre-debs from
   Branden Robinson's site?
  
  Because the upstream build process does not compile a shared version.  Xv
  is at present available only as a static library.
  
   It is needed by applications like xine to view
   VCD or DVD in fullscreenmode.
  
  Yes, and they can link it in statically.
  
 
 Alternatively, you could do the following (as root, in /usr/X11R6/lib):
 ld --whole-archive -shared -o libXxf86dga.so libXxf86dga.a
 ld --whole-archive -shared -o libXv.so libXv.a
 
 This tends to do the trick at least for livid (the last time I checked).

Yes, thanks I know this, but why I have to create this on every
machine and then it is not integrated in the package-database,
next upgrade to xfree 4.1 and I will have trouble, when I forgotten
it. After an email to SuSE ([EMAIL PROTECTED]) they have included
this shared version's of libraries in their XFree-packages.

cya
Waldemar

-- 
* A good website for linuxsoftware:|  (o_  *
*   http://www.freshmeat.net   |  //\  *
*   Linux rulez!;-)|  V_/_ *
* GnuPG-Key: 0xBE21BD90 | Tux: #155220 | ICQ: 64035650 *



Xv client library: shared version?

2001-04-13 Thread Juliusz Chroboczek
Dear Mark,

There has been some discussion recently on the Debian list devoted to
maintaining X (see CC) about the lack of a shared version of the Xv
library.  There would appear to be an opinion that shared versions of
the libraries should be included.

Any chance you could drop a note to the list about the rationale for
not including the shared library in the default XFree86 build, and
whether you think there may be any issues with including such a
library in the Debian version?

Thanks,

Juliusz



Re: XFree 4.0.3 debs

2001-04-13 Thread Branden Robinson
On Fri, Apr 13, 2001 at 07:11:49PM +0200, Waldemar Brodkorb wrote:
 * Branden wrote:
 
  On Wed, Apr 11, 2001 at 04:22:38PM +0200, Waldemar Brodkorb wrote:
   Why libXv.so is not integrated in the new pre-debs from
   Branden Robinson's site?
  
  Because the upstream build process does not compile a shared version.  Xv
  is at present available only as a static library.
 
 Is this the only reason? 
 You could put this in host.def :
 #define SharedLibXxf86dga   YES
 #define SharedLibXv YES 

I could (actually, the correct place is linux.cf, inside #if
LinuxDistribution == LinuxDebian), but I won't.  Not without a better
reason than you're giving me.

To understand why, I suggest reviewing the package descriptions of xlibs
and xlibs-dev.

I don't deviate from upstream practice gratuitously.

-- 
G. Branden Robinson |
Debian GNU/Linux|Bother, said Pooh, as he was
[EMAIL PROTECTED]  |assimilated by the Borg.
http://www.debian.org/~branden/ |


pgp4Uh0OCGHXS.pgp
Description: PGP signature


Re: XF86Config-4 not generated

2001-04-13 Thread Branden Robinson
On Fri, Apr 13, 2001 at 01:57:52PM +0100, Dave Swegen wrote:
 I found this problem too. What I found is that I had to run dexconf
 after the configuration was done. Mind you, the config it generated was
 broken with regards to the pointer section...
 
 Cheers
   Dave
 
 On Fri, Apr 13, 2001 at 01:07:30PM +0400, Ilya Martynov wrote:
  
  CS Hi,
  CS since I did not find an /etc/X11/XF86Config-4 file after upgrading to X
  CS Windows (4.0.2-7), I did
  
  CS dpkg-reconfigure xserver-free86
  
  CS answered all the questions, and expected that a new XF86Config-4 would 
  be
  CS produced.  But still no, I could not find any file of that name on my 
  whole
  CS system...
  
  CS (I know that I can just run xf86config myself.  I'm just wondering if 
  that
  CS is a bug in Debian's config scripts...)
  
  I just want to say: I saw it too. IMHO it is a bug.

You guys will find that these problems is fixed in 4.0.2-13...

-- 
G. Branden Robinson |   No math genius, eh?  Then perhaps you
Debian GNU/Linux|   could explain to me where you got
[EMAIL PROTECTED]  |   these...
http://www.debian.org/~branden/ | PENROSE TILES!


pgpaqYrwgqDGt.pgp
Description: PGP signature


FreeType2 library built from xfree86_4.0.3.deb's source

2001-04-13 Thread ISHIKAWA Mutsumi

 I've checked and rebuilt Branden's test release
xfree86_4.0.3-0pre1v2.deb. And I found a minor problem.

 XFree86 4.0.3 includes FreeType2 library and it will be built
When defined `HasFreetype2 NO'. The default setting is
`HasFreetype2 NO' and test release package does not change the
setting. 

 Building FreeType2 is not needed because Debian has the FreeType2
library (libfreetype6 and libfreetype6-dev).

 So please add `#define HasFreetype2 YES' line in config/cf/linux.cf
(perhaps it is need to modify debian/patches/005_linux_config.diff to
add it).

Tnanks,
--
ISHIKAWA Mutsumi
 [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]





Re: FreeType2 library built from xfree86_4.0.3.deb's source

2001-04-13 Thread Branden Robinson
On Sat, Apr 14, 2001 at 03:21:01AM +0900, ISHIKAWA Mutsumi wrote:
  I've checked and rebuilt Branden's test release
 xfree86_4.0.3-0pre1v2.deb. And I found a minor problem.
 
  XFree86 4.0.3 includes FreeType2 library and it will be built
 When defined `HasFreetype2 NO'. The default setting is
 `HasFreetype2 NO' and test release package does not change the
 setting. 
 
  Building FreeType2 is not needed because Debian has the FreeType2
 library (libfreetype6 and libfreetype6-dev).
 
  So please add `#define HasFreetype2 YES' line in config/cf/linux.cf
 (perhaps it is need to modify debian/patches/005_linux_config.diff to
 add it).

Thanks for pointing this out, Ishikawa-san[1].  I'll make this change right
away, so that it will go into 4.0.3-1.

[1] I hope I got the honorific correct.

-- 
G. Branden Robinson |Murphy's Guide to Science:
Debian GNU/Linux|If it's green or squirms, it's biology.
[EMAIL PROTECTED]  |If it stinks, it's chemistry.
http://www.debian.org/~branden/ |If it doesn't work, it's physics.


pgptLpseTISvc.pgp
Description: PGP signature


Re: Xv client library: shared version?

2001-04-13 Thread Mark Vojkovich
On 13 Apr 2001, Juliusz Chroboczek wrote:

 Dear Mark,
 
 There has been some discussion recently on the Debian list devoted to
 maintaining X (see CC) about the lack of a shared version of the Xv
 library.  There would appear to be an opinion that shared versions of
 the libraries should be included.
 
 Any chance you could drop a note to the list about the rationale for
 not including the shared library in the default XFree86 build, and
 whether you think there may be any issues with including such a
 library in the Debian version?
 

  It's not an X-consortium standard, or even a de-facto standard.
If you have an app that links against Xv, it won't even start
unless you have the libraries on your machine.  That would prohibit
using that app with anything other than an XFree86 4.x installation. 

   Say you had an app that wanted to use Xv if available, and do
its own software scaling/color conversion otherwise so it would
work on XiG's server or with 3.3.x.  If you called XvQueryExtension
to find if the extension was available your app will not run.
Debian can include a shared library if they want, but applications
wanting to optionally use Xv would be wise to compile with the static 
version.


Mark.



Re: Xv client library: shared version?

2001-04-13 Thread Branden Robinson
On Fri, Apr 13, 2001 at 10:53:54AM -0700, Mark Vojkovich wrote:
   It's not an X-consortium standard, or even a de-facto standard.
 If you have an app that links against Xv, it won't even start
 unless you have the libraries on your machine.  That would prohibit
 using that app with anything other than an XFree86 4.x installation. 
 
Say you had an app that wanted to use Xv if available, and do
 its own software scaling/color conversion otherwise so it would
 work on XiG's server or with 3.3.x.  If you called XvQueryExtension
 to find if the extension was available your app will not run.
 Debian can include a shared library if they want, but applications
 wanting to optionally use Xv would be wise to compile with the static 
 version.

Good enough reasoning for me.  I've actually been arguing against shipping
a shared version in Debian's packages until the XFree86 build process does
so, but some of my users are harassing me to do otherwise.

Thanks for the explanation, Mark.

-- 
G. Branden Robinson |You live and learn.
Debian GNU/Linux|Or you don't live long.
[EMAIL PROTECTED]  |-- Robert Heinlein
http://www.debian.org/~branden/ |


pgpkfpZo3FZKD.pgp
Description: PGP signature