Bug 117635

Summary:	y2pmbuild does not support BuildRequires separated with ","
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Pascal Bleser <pascal.bleser>
Component:	Development	Assignee:	Ludwig Nussel <lnussel>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P5 - None	CC:	lnussel
Version:	RC 1
Target Milestone:	---
Hardware:	x86
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Pascal Bleser 2005-09-17 16:35:11 UTC

I noticed that y2pmbuild, when analyzing the BuildRequires tags inside a spec
file, does not support having packages separated with "," and only works
properly when they're separated by " "

Example:
BuildRequires: python, kdelibs3, kdelibs3-devel >= 3.2.0, make

y2pmbuild will complain that "package python, is not available." and "package
kdelibs3, is not available."

It's not a show-stopper, I can modify my spec files to have only
whitespace-separated tokens in BuildRequires, but IMHO it's a bug nevertheless,
as rpmbuild supports both notations (the BuildRequires example above works fine
with plain rpmbuild).

Comment 1 Ludwig Nussel 2005-09-19 14:32:42 UTC

the spec file gets "parsed" by a shell script. It's the most primitive parser  
one can think of. It doesn't matter with SUSE generates spec files as there  
never are version operators in buildrequires. I'll close this as WONTFIX, I  
don't consider it as bug but as missing feature. I am aware that this should  
be improved some time.

Comment 2 Pascal Bleser 2005-09-19 14:50:22 UTC

(In reply to comment #1)

I don't quite agree:
- RPM (rpmbuild) supports both having ","-separated entries *and* specifying
version requirements in BuildRequires, which is quite sensible (e.g.
BuildRequires:kdelibs3-devel >= 3.2.0), at lease when you write src.rpm files
that are supposed to build on several SUSE versions (which Novell doesn't do,
but e.g. Packman and I heavily rely on that)
- the fact that it's "sufficient for SUSE spec files" isn't valid either, as
Novell is propagating y2pmbuild as the build tool for the openSUSE community('s
packagers)

I could understand "LATER" because noone has the time for that now, or "WONTFIX"
if you're currently working on a replacement for y2pmbuild. That would be fine
and understandable.

Nevertheless, I'll see if I have some time to provide a patch for it.
Until then, I can't use y2pmbuild for my RPMs, and I run the 2nd largest 3rd
package repository for SUSE Linux, so it's a bit of a shame. But oh well, nevermind.