[opensuse-packaging] Warning: makeinfo was splitted off from texinfo
Hi, for all of those packages which uses BuildRequires: texinfo or hope on the standard build environment providing texinfo, please use BuildRequires: makeinfo as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s). For packages depending texinfo tools like texi2dvi the required TeXLive packages will be installed if and only if the packages texlive-specs-a upto texlive-specs-z and texlive will be part of openSUSE:Factory. With this we have than the same package structure as TeXLive upstream already provides (more than 6000 packages:). Thanks Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi,
for all of those packages which uses
BuildRequires: texinfo
or hope on the standard build environment providing texinfo, please use
BuildRequires: makeinfo
as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s). Note that you do not need to %suse_version that as the old texinfo
On 18.07.2012 11:12, Dr. Werner Fink wrote: provided makeinfo too Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wed, 18 Jul 2012, Stephan Kulow wrote:
Hi,
for all of those packages which uses
BuildRequires: texinfo
or hope on the standard build environment providing texinfo, please use
BuildRequires: makeinfo
as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s). Note that you do not need to %suse_version that as the old texinfo
On 18.07.2012 11:12, Dr. Werner Fink wrote: provided makeinfo too
Only for 12.1 and newer, older versions did not have the provide.
Richard.
--
Richard Guenther
On 18.07.2012 12:40, Richard Guenther wrote:
On Wed, 18 Jul 2012, Stephan Kulow wrote:
Hi,
for all of those packages which uses
BuildRequires: texinfo
or hope on the standard build environment providing texinfo, please use
BuildRequires: makeinfo
as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s). Note that you do not need to %suse_version that as the old texinfo
On 18.07.2012 11:12, Dr. Werner Fink wrote: provided makeinfo too
Only for 12.1 and newer, older versions did not have the provide.
Ok, so wait for 2 months after 12.2 release to remove the 11.4 case :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wednesday 18 July 2012, Dr. Werner Fink wrote:
Hi,
for all of those packages which uses
BuildRequires: texinfo
or hope on the standard build environment providing texinfo, please use
BuildRequires: makeinfo
as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s).
For packages depending texinfo tools like texi2dvi the required TeXLive packages will be installed if and only if the packages texlive-specs-a upto texlive-specs-z and texlive will be part of openSUSE:Factory. With this we have than the same package structure as TeXLive upstream already provides (more than 6000 packages:).
Hm, installing a complete texlive-bin takes ages now ... I see that splitting all these texlive packages could be nice for OBS build systems if it would speed up things. In practice the split is just annoying. For example installing texlive-dvips for Factory takes much much longer than installing texlive-bin on 11.4. cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hm, installing a complete texlive-bin takes ages now ... I had the same problem... as a workaround... I uninstalled all the texlive packages and then triggered a new install only of the pattern I needed... that did the trick.
regards, Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
forgot above zypper se texlive-collection to see what is available. Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Jul 24, 2012 at 11:55:12AM +0200, Ruediger Meier wrote:
On Wednesday 18 July 2012, Dr. Werner Fink wrote:
Hi,
for all of those packages which uses
BuildRequires: texinfo
or hope on the standard build environment providing texinfo, please use
BuildRequires: makeinfo
as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s).
For packages depending texinfo tools like texi2dvi the required TeXLive packages will be installed if and only if the packages texlive-specs-a upto texlive-specs-z and texlive will be part of openSUSE:Factory. With this we have than the same package structure as TeXLive upstream already provides (more than 6000 packages:).
Hm, installing a complete texlive-bin takes ages now ... I see that splitting all these texlive packages could be nice for OBS build systems if it would speed up things. In practice the split is just annoying. For example installing texlive-dvips for Factory takes much much longer than installing texlive-bin on 11.4.
This is a problem of libzypp as it runs after every texlive package the posttrans scriplet instead of doing this after the transaction is complete. I'm touching files below /var/run/texlive in the post and postun scriplets which will checked in the posttrans scriplet by the update script. If the all posttrans scriptlets would be executed after all texlive packages had been installed then the update script would run only once (e.g. doing texhash, fmtutils-sys, updmap-sys, ..., and removing the control files below /var/run/texlive). To support posttrans in libzypp the rpm has to know about --noposttrans as with this option libzypp can cause rpm to skip the posttrans scriptlet to be able to do this job at its own. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 24 July 2012, Dr. Werner Fink wrote:
On Tue, Jul 24, 2012 at 11:55:12AM +0200, Ruediger Meier wrote:
On Wednesday 18 July 2012, Dr. Werner Fink wrote:
Hi,
for all of those packages which uses
BuildRequires: texinfo
or hope on the standard build environment providing texinfo, please use
BuildRequires: makeinfo
as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s).
For packages depending texinfo tools like texi2dvi the required TeXLive packages will be installed if and only if the packages texlive-specs-a upto texlive-specs-z and texlive will be part of openSUSE:Factory. With this we have than the same package structure as TeXLive upstream already provides (more than 6000 packages:).
Hm, installing a complete texlive-bin takes ages now ... I see that splitting all these texlive packages could be nice for OBS build systems if it would speed up things. In practice the split is just annoying. For example installing texlive-dvips for Factory takes much much longer than installing texlive-bin on 11.4.
This is a problem of libzypp as it runs after every texlive package the posttrans scriplet instead of doing this after the transaction is complete. I'm touching files below /var/run/texlive in the post and postun scriplets which will checked in the posttrans scriplet by the update script. If the all posttrans scriptlets would be executed after all texlive packages had been installed then the update script would run only once (e.g. doing texhash, fmtutils-sys, updmap-sys, ..., and removing the control files below /var/run/texlive).
To support posttrans in libzypp the rpm has to know about --noposttrans as with this option libzypp can cause rpm to skip the posttrans scriptlet to be able to do this job at its own.
Is zypper used at all to install the local osc build systems? BTW will the split make it already into 12.2? So should we check for suse_version > 1220 or >= 1220? cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Jul 24, 2012 at 01:06:55PM +0200, Ruediger Meier wrote:
Is zypper used at all to install the local osc build systems? BTW will the split make it already into 12.2? So should we check for suse_version > 1220 or >= 1220?
you may use > 1220 or >= 1230 Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 24 July 2012, Ruediger Meier wrote:
On Wednesday 18 July 2012, Dr. Werner Fink wrote:
Hi,
for all of those packages which uses
BuildRequires: texinfo
or hope on the standard build environment providing texinfo, please use
BuildRequires: makeinfo
as the makeinfo utility has been split off from texinfo package to avoid that TeXLive packages will be installed for generating simple info file(s).
For packages depending texinfo tools like texi2dvi the required TeXLive packages will be installed if and only if the packages texlive-specs-a upto texlive-specs-z and texlive will be part of openSUSE:Factory. With this we have than the same package structure as TeXLive upstream already provides (more than 6000 packages:).
Hm, installing a complete texlive-bin takes ages now ... I see that splitting all these texlive packages could be nice for OBS build systems if it would speed up things. In practice the split is just annoying. For example installing texlive-dvips for Factory takes much much longer than installing texlive-bin on 11.4.
To add some numbers... On a usual core2 machine the osc build installation part of these (BTW now strange looking) BuildRequires from my sbcl package ... %if 0%{?fedora_version:1} BuildRequires: texinfo-tex %else BuildRequires: texinfo %endif %if 0%{?suse_version} >= 1220 || 0%{?fedora_version:1} BuildRequires: texlive-dvips %else BuildRequires: texlive-bin %endif ... takes about 9 minutes on openSUSE_Factory in comparision to 1 minute on openSUSE_12.1. When re-using the build root for packages with and without texlive deps then the relative contrast is even bigger. This is IMO just not acceptable. cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Jul 24, 2012 at 01:49:30PM +0200, Ruediger Meier wrote:
To add some numbers... On a usual core2 machine the osc build installation part of these (BTW now strange looking) BuildRequires from my sbcl package ...
%if 0%{?fedora_version:1} BuildRequires: texinfo-tex %else BuildRequires: texinfo %endif %if 0%{?suse_version} >= 1220 || 0%{?fedora_version:1} BuildRequires: texlive-dvips %else BuildRequires: texlive-bin %endif
... takes about 9 minutes on openSUSE_Factory in comparision to 1 minute on openSUSE_12.1. When re-using the build root for packages with and without texlive deps then the relative contrast is even bigger. This is IMO just not acceptable.
It has me taken three months in parallel to my normal job to make TeXLive 2012 compatible with the upstream package scheme. In fact I'm using the upstream package data base to generate with the help of some larger perl scripts the packages including fetching source tar balls, generating spec files, incooperate patches, and further dependencies, ... I'll not go back from this point. This is problem of libzypp used by zypper and YaST. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 24 July 2012, Dr. Werner Fink wrote:
On Tue, Jul 24, 2012 at 01:49:30PM +0200, Ruediger Meier wrote:
To add some numbers... On a usual core2 machine the osc build installation part of these (BTW now strange looking) BuildRequires from my sbcl package ...
%if 0%{?fedora_version:1} BuildRequires: texinfo-tex %else BuildRequires: texinfo %endif %if 0%{?suse_version} >= 1220 || 0%{?fedora_version:1} BuildRequires: texlive-dvips %else BuildRequires: texlive-bin %endif
... takes about 9 minutes on openSUSE_Factory in comparision to 1 minute on openSUSE_12.1. When re-using the build root for packages with and without texlive deps then the relative contrast is even bigger. This is IMO just not acceptable.
It has me taken three months in parallel to my normal job to make TeXLive 2012 compatible with the upstream package scheme. In fact I'm using the upstream package data base to generate with the help of some larger perl scripts the packages including fetching source tar balls, generating spec files, incooperate patches, and further dependencies, ... I'll not go back from this point.
This is problem of libzypp used by zypper and YaST.
Hm, for my understanding we are using rpm binary packages to have more comfort and speed. If we have now thousands of texlive packages which slows down any rpm related operation and makes it more complicated for the usual user who just wants to have working tex stuff then mission has failed. What is the benefit of having all these separate texlive rpms? I'd say the usual user will install either all or none anyway. cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Jul 24, 2012 at 03:06:30PM +0200, Ruediger Meier wrote:
Hm, for my understanding we are using rpm binary packages to have more comfort and speed. If we have now thousands of texlive packages which slows down any rpm related operation and makes it more complicated for the usual user who just wants to have working tex stuff then mission has failed.
What is the benefit of having all these separate texlive rpms? I'd say the usual user will install either all or none anyway.
Smaller TeXLive installations like it upstream, Debian, and RedHat. I had several bug report in past to follow the package upstream scheme and now I've done it. IMHO rpm as well as libzypp as to be fixed to be able to do posttrans scriptlets as described in the current rpm manual. If you would use rpm standalone without zypper in *one* transaction for all texlive packages it would be much faster. The only problem is that rpm can not expand dependencies like libzypp. Beside this: ever read rpm source code, if you think about comfort and speed ;) Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 24 July 2012 14:21, Dr. Werner Fink
On Tue, Jul 24, 2012 at 03:06:30PM +0200, Ruediger Meier wrote:
Hm, for my understanding we are using rpm binary packages to have more comfort and speed. If we have now thousands of texlive packages which slows down any rpm related operation and makes it more complicated for the usual user who just wants to have working tex stuff then mission has failed.
What is the benefit of having all these separate texlive rpms? I'd say the usual user will install either all or none anyway.
Smaller TeXLive installations like it upstream, Debian, and RedHat. I had several bug report in past to follow the package upstream scheme and now I've done it.
IMHO rpm as well as libzypp as to be fixed to be able to do posttrans scriptlets as described in the current rpm manual.
If you would use rpm standalone without zypper in *one* transaction for all texlive packages it would be much faster. The only problem is that rpm can not expand dependencies like libzypp.
Beside this: ever read rpm source code, if you think about comfort and speed ;)
Where would be the benefit of a --noposttrans option? ZYpp could just install all the packages in a single rpm transaction. But don't hold your breath: http://lists.opensuse.org/opensuse-factory/2011-04/msg00339.html In any case, Werner is correct and that's something we would like to have anyway for other things (updating GTK icon cache, etc.). The fix/feature, whatever the form, is missing in libzypp... I didn't look at the TeXLive packages, but as a workaround perhaps you can use "update scripts": http://en.opensuse.org/openSUSE:Maintenance/Code11/Howto#Out_of_transaction_... Last time I checked they weren't exactly the same and were badly underdocumented, but perhaps in this specific case they can help. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 24 July 2012 14:47, Cristian Morales Vega
I didn't look at the TeXLive packages, but as a workaround perhaps you can use "update scripts": http://en.opensuse.org/openSUSE:Maintenance/Code11/Howto#Out_of_transaction_... Last time I checked they weren't exactly the same and were badly underdocumented, but perhaps in this specific case they can help.
The documentation linked from the source code is this -> http://old-en.opensuse.org/Software_Management/Code11/Scripts_and_Messages -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (6)
-
Alin M Elena -
Cristian Morales Vega -
Dr. Werner Fink -
Richard Guenther -
Ruediger Meier -
Stephan Kulow