It took me some time but I think I still have not managed to
fully digest this discussion.
I am in the hope that both the Fedora Perl packagers and
CPAN authors would prefer to eliminate as much of the
manual work required by the packagers as possible.
One of the biggest complaints about Perl I
On 02/08/2010 06:10 PM, Gabor Szabo wrote:
Hi,
I saw these bug reports starting to flow in two days ago,
just in time to mention them during my talk on FOSDEM.
The problem seems to be that the rpm builder extracted the list of
dependencies of Padre from its source code. This did not notice
On 02/09/2010 08:10 AM, Ralf Corsepius wrote:
On 02/08/2010 06:10 PM, Gabor Szabo wrote:
Hi,
I saw these bug reports starting to flow in two days ago,
just in time to mention them during my talk on FOSDEM.
The problem seems to be that the rpm builder extracted the list of
dependencies of
Dave,
I prefer don't switch off rpm magic. Sometimes it could help find
new requirements because they are not in Meta or they are in Meta
even if they are not needed anymore.
- Dave Cross d...@dave.org.uk wrote:
Marcela,
cpanspec does the right thing. It creates the list of requires from
- Dave Cross d...@dave.org.uk wrote:
On 02/09/2010 08:10 AM, Ralf Corsepius wrote:
On 02/08/2010 06:10 PM, Gabor Szabo wrote:
Hi,
I saw these bug reports starting to flow in two days ago,
just in time to mention them during my talk on FOSDEM.
The problem seems to be that the
Hello,
as Ralf explained in another thread, there are some specific
requirements for rpm dependencies in Fedora.
In general, we wish that the package, when installed, can be used
in its full strength, so we want to bring in most of the optional
requirements. (We might think about soft
Hi,
I saw these bug reports starting to flow in two days ago,
just in time to mention them during my talk on FOSDEM.
The problem seems to be that the rpm builder extracted the list of
dependencies of Padre from its source code. This did not notice that
Win32::API is use only when running on
Hello,
I want to ask upstream about it ;-)
I used cpanspec for generating spec, but that doesn't help
if rpm automagically creates requires probably from Makefile.
In Makefile.PL are tests like:
requires 'Win32::API' = '0.58' if win32;
but it doesn't seem to work in this case. I was
Marcela,
cpanspec does the right thing. It creates the list of requires from the
list in META.yml.
rpm does the wrong thing by parsing the source code and looking for
use statements.
My advice is to trust cpanspec and not to use the rpm dependency
auto-generation. I do this by adding:
