Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:10:19PM -0500, Steve M. Robbins wrote:
What I am proposing is a source package that generates *both* a "main"
and a "contrib" .deb. What would the autobuilder do with that? In
fact, how would the autobuilder even know that is the case? The
I guess it depends on the source only. If the autobuilder finds the source
in main, it builds the package. If its not in main, it does not know about
it. If your package creates also a contrib deb, I think the source can not
be in main, right? So it will not be autobuilt.
You were asking for geomview? Its in the needs-build list on m68k, buildd
tried it but (seems the web interface does not work anymore?):
Automatic build of geomview_1.8.0-5 on kullervo by sbuild 1.152
Build started at 20010305-1546
**
Fetching .dsc file...
** Using build dependencies supplied by package:
Build-Depends: debhelper, autoconf, automake, flex, bison, lesstif-dev, libgl-dev,
tetex-bin, texi2html
** Filtered missing central deps that are build-essential: libstdc++2.10-dev
** Filtered missing central deps that are dependencies of or provide build-deps:
mesag-dev, xlibs-dev (= 4.0.1-11)
Warning:
The following central src deps are (probably) missing:
groff, tcl8.0-dev, tk8.0-dev
[...]
Checking for source dependency conflicts...
libgl-dev is a virtual package provided by: xlibmesa-dev mesag-dev libutahglx-dev
mesag3+ggi-dev
Using mesag-dev (selected in sbuildrc)
/usr/bin/sudo /usr/bin/apt-get $CHROOT_OPTIONS -q -y install lesstif-dev libgl-dev
texi2html
Reading Package Lists...
Building Dependency Tree...
Package libgl-dev is a virtual package provided by:
xlibmesa-dev 4.0.2-4
mesag-dev 3.2-1
libutahglx-dev 0.0-cvs-20001110-1
mesag3+ggi-dev 3.1-12
You should explicitly select one to install.
E: Package libgl-dev has no installation candidate
libgl-dev is a virtual package provided by: xlibmesa-dev mesag-dev libutahglx-dev
mesag3+ggi-dev
Using mesag-dev (selected in sbuildrc)
[...]
# Add here commands to configure the package.
CFLAGS='-O2' ./configure --prefix=/usr --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --without-xforms
[...]
checking for IceConnectionNumber in -lICE... yes
checking for Xmu... yes
checking for motif... configure: error:
Can't find Motif header file Xm/Xm.h. Geomview requires Motif
(or Lesstif). See the file INSTALL.Geomview for details.
Hmm? lesstif-dev was installed...
If this package also builds with xforms, you have to mention it with the
build-depends? Plus, I think (policy experts correct me) the source does not
belong into main. But I think in that case, you should compile it yourself
on an m68k box (or maybe ask the xforms maintainer)
Christian
--
http://people.debian.org/~cts/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to build a package conditionally?
* Steve M Robbins [EMAIL PROTECTED] wrote: Hi, What I am proposing is a source package that generates *both* a "main" and a "contrib" .deb. This is not allowed. One source package can only build packages for one section. See, the structure on the FTP sites reflects this: dist - main- i386 etc. - source - contrib - i386 etc. - source Debian strictly only contains main (which is self-containing). Therefore the source has to be in main. But if the package would also generate a contrib package, there would be a package in this section without a a source package. You have to split the source into two source packages for this. Ciao, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to build a package conditionally?
On Tue, 06 Mar 2001, Martin Bialasinski wrote: * Steve M Robbins [EMAIL PROTECTED] wrote: What I am proposing is a source package that generates *both* a "main" and a "contrib" .deb. This is not allowed. Or rather, it is... kinda. You can have your source package generate two sets of .debs depending on how it is built, but you must upload it twice, with different names (and building different sets of debs by default) to every section. See the fetchmail and fetchmail-ssl source packages for an example. fetchmail-ssl is an automated transform of the fetchmail source package, triggered by "make debian/rules select-ssl". You gain nothing in upload time, but it certains give you less hassle to only have one single source tree in CVS, for example. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh PGP signature
Re: how to build a package conditionally?
On Tue, Mar 06, 2001 at 06:54:31PM -0300, Henrique M Holschuh wrote: On Tue, 06 Mar 2001, Martin Bialasinski wrote: * Steve M Robbins [EMAIL PROTECTED] wrote: What I am proposing is a source package that generates *both* a "main" and a "contrib" .deb. This is not allowed. Or rather, it is... kinda. You can have your source package generate two sets of .debs depending on how it is built, but you must upload it twice, with different names (and building different sets of debs by default) to every section. See the fetchmail and fetchmail-ssl source packages for an example. fetchmail-ssl is an automated transform of the fetchmail source package, triggered by "make debian/rules select-ssl". Ah, thanks! I knew I couldn't be the first to run into this situation. You gain nothing in upload time, but it certains give you less hassle to only have one single source tree in CVS, for example. Yeah, it's a cute hack. Too bad that the entire source needs to be duplicated, though. -S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to build a package conditionally?
On Tue, Mar 06, 2001 at 06:21:19AM -0600, Christian T. Steigies wrote: On Mon, Mar 05, 2001 at 01:10:19PM -0500, Steve M. Robbins wrote: Can't find Motif header file Xm/Xm.h. Geomview requires Motif (or Lesstif). See the file INSTALL.Geomview for details. Hmm? lesstif-dev was installed... Odd. The log suggests that the same version of libtiff-dev is installed as the one I use, and Xm/Xm.h is in /usr/X11R6/include. I found the full build log on the web, and I see this bit: checking for X... libraries /usr/X11R6/lib, headers whereas, on my i386, I get checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include So, the question becomes: why does the configuration on m68k not require -I/usr/X11R6/include to find the other X headers? If this package also builds with xforms, you have to mention it with the build-depends? Most of the packages does NOT require xforms. The bits that do require it are currently unbuilt. So it resides in main. It looks like if I want to make a second "contrib" .deb, I need to manufacture a second source package. Ugh. -S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to build a package conditionally?
On Tue, 06 Mar 2001, Steve M. Robbins wrote: On Tue, Mar 06, 2001 at 06:54:31PM -0300, Henrique M Holschuh wrote: You gain nothing in upload time, but it certains give you less hassle to only have one single source tree in CVS, for example. Yeah, it's a cute hack. Too bad that the entire source needs to be duplicated, though. AFAIK, it is a policy requirement. Every section of the archive (main, contrib, non-free, non-US/main, non-US/contrib, non-US/non-free) must have separate source packages. Maybe it could be changed/ignored for main/contrib pairs, but non-free and non-US/* always require separate source packages. Some of the stuff that can go inside a non-free source package is not allowed even inside main/contrib packages (requiring you to delete them from the package in main/contrib, and keep it in the non-free one)... I'm happy enough I can build fetchmail and fetchmail-ssl with one shell script, and deal with only one source tree... cute hack or not :P -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh PGP signature
Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:10:19PM -0500, Steve M. Robbins wrote:
What I am proposing is a source package that generates *both* a main
and a contrib .deb. What would the autobuilder do with that? In
fact, how would the autobuilder even know that is the case? The
I guess it depends on the source only. If the autobuilder finds the source
in main, it builds the package. If its not in main, it does not know about
it. If your package creates also a contrib deb, I think the source can not
be in main, right? So it will not be autobuilt.
You were asking for geomview? Its in the needs-build list on m68k, buildd
tried it but (seems the web interface does not work anymore?):
Automatic build of geomview_1.8.0-5 on kullervo by sbuild 1.152
Build started at 20010305-1546
**
Fetching .dsc file...
** Using build dependencies supplied by package:
Build-Depends: debhelper, autoconf, automake, flex, bison, lesstif-dev,
libgl-dev, tetex-bin, texi2html
** Filtered missing central deps that are build-essential: libstdc++2.10-dev
** Filtered missing central deps that are dependencies of or provide
build-deps: mesag-dev, xlibs-dev (= 4.0.1-11)
Warning:
The following central src deps are (probably) missing:
groff, tcl8.0-dev, tk8.0-dev
[...]
Checking for source dependency conflicts...
libgl-dev is a virtual package provided by: xlibmesa-dev mesag-dev
libutahglx-dev mesag3+ggi-dev
Using mesag-dev (selected in sbuildrc)
/usr/bin/sudo /usr/bin/apt-get $CHROOT_OPTIONS -q -y install lesstif-dev
libgl-dev texi2html
Reading Package Lists...
Building Dependency Tree...
Package libgl-dev is a virtual package provided by:
xlibmesa-dev 4.0.2-4
mesag-dev 3.2-1
libutahglx-dev 0.0-cvs-20001110-1
mesag3+ggi-dev 3.1-12
You should explicitly select one to install.
E: Package libgl-dev has no installation candidate
libgl-dev is a virtual package provided by: xlibmesa-dev mesag-dev
libutahglx-dev mesag3+ggi-dev
Using mesag-dev (selected in sbuildrc)
[...]
# Add here commands to configure the package.
CFLAGS='-O2' ./configure --prefix=/usr --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --without-xforms
[...]
checking for IceConnectionNumber in -lICE... yes
checking for Xmu... yes
checking for motif... configure: error:
Can't find Motif header file Xm/Xm.h. Geomview requires Motif
(or Lesstif). See the file INSTALL.Geomview for details.
Hmm? lesstif-dev was installed...
If this package also builds with xforms, you have to mention it with the
build-depends? Plus, I think (policy experts correct me) the source does not
belong into main. But I think in that case, you should compile it yourself
on an m68k box (or maybe ask the xforms maintainer)
Christian
--
http://people.debian.org/~cts/
Re: how to build a package conditionally?
* Steve M Robbins [EMAIL PROTECTED] wrote: Hi, What I am proposing is a source package that generates *both* a main and a contrib .deb. This is not allowed. One source package can only build packages for one section. See, the structure on the FTP sites reflects this: dist - main- i386 etc. - source - contrib - i386 etc. - source Debian strictly only contains main (which is self-containing). Therefore the source has to be in main. But if the package would also generate a contrib package, there would be a package in this section without a a source package. You have to split the source into two source packages for this. Ciao, Martin
Re: how to build a package conditionally?
On Tue, 06 Mar 2001, Martin Bialasinski wrote: * Steve M Robbins [EMAIL PROTECTED] wrote: What I am proposing is a source package that generates *both* a main and a contrib .deb. This is not allowed. Or rather, it is... kinda. You can have your source package generate two sets of .debs depending on how it is built, but you must upload it twice, with different names (and building different sets of debs by default) to every section. See the fetchmail and fetchmail-ssl source packages for an example. fetchmail-ssl is an automated transform of the fetchmail source package, triggered by make debian/rules select-ssl. You gain nothing in upload time, but it certains give you less hassle to only have one single source tree in CVS, for example. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh pgpTaI62Wj3bS.pgp Description: PGP signature
Re: how to build a package conditionally?
On Tue, Mar 06, 2001 at 06:54:31PM -0300, Henrique M Holschuh wrote: On Tue, 06 Mar 2001, Martin Bialasinski wrote: * Steve M Robbins [EMAIL PROTECTED] wrote: What I am proposing is a source package that generates *both* a main and a contrib .deb. This is not allowed. Or rather, it is... kinda. You can have your source package generate two sets of .debs depending on how it is built, but you must upload it twice, with different names (and building different sets of debs by default) to every section. See the fetchmail and fetchmail-ssl source packages for an example. fetchmail-ssl is an automated transform of the fetchmail source package, triggered by make debian/rules select-ssl. Ah, thanks! I knew I couldn't be the first to run into this situation. You gain nothing in upload time, but it certains give you less hassle to only have one single source tree in CVS, for example. Yeah, it's a cute hack. Too bad that the entire source needs to be duplicated, though. -S
Re: how to build a package conditionally?
On Tue, Mar 06, 2001 at 06:21:19AM -0600, Christian T. Steigies wrote: On Mon, Mar 05, 2001 at 01:10:19PM -0500, Steve M. Robbins wrote: Can't find Motif header file Xm/Xm.h. Geomview requires Motif (or Lesstif). See the file INSTALL.Geomview for details. Hmm? lesstif-dev was installed... Odd. The log suggests that the same version of libtiff-dev is installed as the one I use, and Xm/Xm.h is in /usr/X11R6/include. I found the full build log on the web, and I see this bit: checking for X... libraries /usr/X11R6/lib, headers whereas, on my i386, I get checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include So, the question becomes: why does the configuration on m68k not require -I/usr/X11R6/include to find the other X headers? If this package also builds with xforms, you have to mention it with the build-depends? Most of the packages does NOT require xforms. The bits that do require it are currently unbuilt. So it resides in main. It looks like if I want to make a second contrib .deb, I need to manufacture a second source package. Ugh. -S
Re: how to build a package conditionally?
On Tue, 06 Mar 2001, Steve M. Robbins wrote: On Tue, Mar 06, 2001 at 06:54:31PM -0300, Henrique M Holschuh wrote: You gain nothing in upload time, but it certains give you less hassle to only have one single source tree in CVS, for example. Yeah, it's a cute hack. Too bad that the entire source needs to be duplicated, though. AFAIK, it is a policy requirement. Every section of the archive (main, contrib, non-free, non-US/main, non-US/contrib, non-US/non-free) must have separate source packages. Maybe it could be changed/ignored for main/contrib pairs, but non-free and non-US/* always require separate source packages. Some of the stuff that can go inside a non-free source package is not allowed even inside main/contrib packages (requiring you to delete them from the package in main/contrib, and keep it in the non-free one)... I'm happy enough I can build fetchmail and fetchmail-ssl with one shell script, and deal with only one source tree... cute hack or not :P -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh pgpIpJCmeERi8.pgp Description: PGP signature
Re: how to build a package conditionally?
On Sun, Mar 04, 2001 at 08:34:25PM -1000, Brian Russo wrote: On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote: Hi, I'm maintaining a package (geomview) whose source is free, but parts of it require a non-free library (xforms) to compile. Currently, the debian source package builds a single package that omits the programs that require xforms. There is a wishlist bug requesting that a second package be created containing the extra bits. That seems like a reasonable request. How do I do it? last I checked the autobuilders didn't do anything but main, so I don't think should be a problem, affirmation anyone? My understanding of the statement "the autobuilders [don't] do anything but main" is that they only process source packages that generate .debs for the "main" distribution. What I am proposing is a source package that generates *both* a "main" and a "contrib" .deb. What would the autobuilder do with that? In fact, how would the autobuilder even know that is the case? The control file does not record whether a binary goes into main or contrib. [I presume that is decided by the ftp maintainers when a new package is introduced, and then recorded somewhere. Do the autobuilders use this information?] If I set up the "rules" to build both the main and contrib packages unconditionally, would the autobuilders selectively pick out and build only the main package? The Build-depends, in this case, would include a non-free package; wouldn't this cause extra work to override the dependency if the autobuilder is only doing main? -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote:
Hi,
I'm maintaining a package (geomview) whose source is free, but parts
of it require a non-free library (xforms) to compile. Currently, the
debian source package builds a single package that omits the programs
that require xforms. There is a wishlist bug requesting that a second
package be created containing the extra bits. That seems like a
reasonable request. How do I do it?
The current geomview package is in "main", because it is DFSG free.
The second package, however, would need to be in "contrib", since it
uses the non-free "xforms" package. To me, the main problem is that I
don't want to build the second ("geomview-contrib") package
unconditionally, because of the autobuilders. I'd like to have the
default behaviour of running "dpkg-buildpackage" to be that only the
main geomview package is built. But one should be able to trigger a
build of both the main and the contrib packages.
Is there a recommended way to achieve this?
Actually.. fltk is supposed to be an xforms replacement. If geomview
could build against that, you wouldn't have to bother with contrib.
-- Ferret
Who has no idea if fltk is 100% xforms-compatible.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:10:19PM -0500, Steve M. Robbins wrote: On Sun, Mar 04, 2001 at 08:34:25PM -1000, Brian Russo wrote: On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote: Hi, I'm maintaining a package (geomview) whose source is free, but parts of it require a non-free library (xforms) to compile. Currently, the debian source package builds a single package that omits the programs that require xforms. There is a wishlist bug requesting that a second package be created containing the extra bits. That seems like a reasonable request. How do I do it? last I checked the autobuilders didn't do anything but main, so I don't think should be a problem, affirmation anyone? My understanding of the statement "the autobuilders [don't] do anything but main" is that they only process source packages that generate .debs for the "main" distribution. What I am proposing is a source package that generates *both* a "main" and a "contrib" .deb. What would the autobuilder do with that? In fact, how would the autobuilder even know that is the case? The control file does not record whether a binary goes into main or contrib. [I presume that is decided by the ftp maintainers when a new package is introduced, and then recorded somewhere. Do the autobuilders use this information?] hmm, I don't know, I presume they get the information ala madison via auric. or a similar mechanism, I was kind of hoping someone would chime in and give you the answer :) Probably the easiest thing would be to break it into a separate package. - Brian who knows that the autobuilders only process main but is unsure of the details. -- Brian Russo [EMAIL PROTECTED] Debian/GNU Linux [EMAIL PROTECTED] http://www.debian.org LPSG "member"[EMAIL PROTECTED] http://www.lpsg.org -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote: Hi, I'm maintaining a package (geomview) whose source is free, but parts of it require a non-free library (xforms) to compile. Currently, the debian source package builds a single package that omits the programs that require xforms. There is a wishlist bug requesting that a second package be created containing the extra bits. That seems like a reasonable request. How do I do it? last I checked the autobuilders didn't do anything but main, so I don't think should be a problem, affirmation anyone? -- Brian Russo [EMAIL PROTECTED] Debian/GNU Linux [EMAIL PROTECTED] http://www.debian.org LPSG member[EMAIL PROTECTED] http://www.lpsg.org -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: how to build a package conditionally?
On Sun, Mar 04, 2001 at 08:34:25PM -1000, Brian Russo wrote: On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote: Hi, I'm maintaining a package (geomview) whose source is free, but parts of it require a non-free library (xforms) to compile. Currently, the debian source package builds a single package that omits the programs that require xforms. There is a wishlist bug requesting that a second package be created containing the extra bits. That seems like a reasonable request. How do I do it? last I checked the autobuilders didn't do anything but main, so I don't think should be a problem, affirmation anyone? My understanding of the statement the autobuilders [don't] do anything but main is that they only process source packages that generate .debs for the main distribution. What I am proposing is a source package that generates *both* a main and a contrib .deb. What would the autobuilder do with that? In fact, how would the autobuilder even know that is the case? The control file does not record whether a binary goes into main or contrib. [I presume that is decided by the ftp maintainers when a new package is introduced, and then recorded somewhere. Do the autobuilders use this information?] If I set up the rules to build both the main and contrib packages unconditionally, would the autobuilders selectively pick out and build only the main package? The Build-depends, in this case, would include a non-free package; wouldn't this cause extra work to override the dependency if the autobuilder is only doing main? -Steve
Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote: Hi, I'm maintaining a package (geomview) whose source is free, but parts of it require a non-free library (xforms) to compile. Currently, the debian source package builds a single package that omits the programs that require xforms. There is a wishlist bug requesting that a second package be created containing the extra bits. That seems like a reasonable request. How do I do it? The current geomview package is in main, because it is DFSG free. The second package, however, would need to be in contrib, since it uses the non-free xforms package. To me, the main problem is that I don't want to build the second (geomview-contrib) package unconditionally, because of the autobuilders. I'd like to have the default behaviour of running dpkg-buildpackage to be that only the main geomview package is built. But one should be able to trigger a build of both the main and the contrib packages. Is there a recommended way to achieve this? Actually.. fltk is supposed to be an xforms replacement. If geomview could build against that, you wouldn't have to bother with contrib. -- Ferret Who has no idea if fltk is 100% xforms-compatible.
Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:10:19PM -0500, Steve M. Robbins wrote: On Sun, Mar 04, 2001 at 08:34:25PM -1000, Brian Russo wrote: On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote: Hi, I'm maintaining a package (geomview) whose source is free, but parts of it require a non-free library (xforms) to compile. Currently, the debian source package builds a single package that omits the programs that require xforms. There is a wishlist bug requesting that a second package be created containing the extra bits. That seems like a reasonable request. How do I do it? last I checked the autobuilders didn't do anything but main, so I don't think should be a problem, affirmation anyone? My understanding of the statement the autobuilders [don't] do anything but main is that they only process source packages that generate .debs for the main distribution. What I am proposing is a source package that generates *both* a main and a contrib .deb. What would the autobuilder do with that? In fact, how would the autobuilder even know that is the case? The control file does not record whether a binary goes into main or contrib. [I presume that is decided by the ftp maintainers when a new package is introduced, and then recorded somewhere. Do the autobuilders use this information?] hmm, I don't know, I presume they get the information ala madison via auric. or a similar mechanism, I was kind of hoping someone would chime in and give you the answer :) Probably the easiest thing would be to break it into a separate package. - Brian who knows that the autobuilders only process main but is unsure of the details. -- Brian Russo [EMAIL PROTECTED] Debian/GNU Linux [EMAIL PROTECTED] http://www.debian.org LPSG member[EMAIL PROTECTED] http://www.lpsg.org -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: how to build a package conditionally?
On Mon, Mar 05, 2001 at 01:28:51AM -0500, Steve M. Robbins wrote: Hi, I'm maintaining a package (geomview) whose source is free, but parts of it require a non-free library (xforms) to compile. Currently, the debian source package builds a single package that omits the programs that require xforms. There is a wishlist bug requesting that a second package be created containing the extra bits. That seems like a reasonable request. How do I do it? last I checked the autobuilders didn't do anything but main, so I don't think should be a problem, affirmation anyone? -- Brian Russo [EMAIL PROTECTED] Debian/GNU Linux [EMAIL PROTECTED] http://www.debian.org LPSG "member"[EMAIL PROTECTED] http://www.lpsg.org -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
