151086 – app-portage/ufed fails to parse make.conf

Bug 151086 - app-portage/ufed fails to parse make.conf

Summary: app-portage/ufed fails to parse make.conf

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Tools (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Harald van Dijk (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-10-12 16:29 UTC by Dustin Polke
Modified:	2006-10-13 13:56 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Diff of make.conf with working and not working line (make.conf.diff,508 bytes, text/plain) 2006-10-12 16:33 UTC, Dustin Polke	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dustin Polke 2006-10-12 16:29:59 UTC

Ufed fails to parse make.conf if a comment in make.conf begins directly after quotation mark. For example, see attached diff file.

Error message:

solaris dustin # ufed
Parse error in /etc/make.conf
Compilation failed in require at /usr/sbin/ufed line 9.
BEGIN failed--compilation aborted at /usr/sbin/ufed line 9.

Comment 1 Dustin Polke 2006-10-12 16:33:01 UTC

Created attachment 99488 [details]
Diff of make.conf with working and not working line

Comment 2 Dustin Polke 2006-10-13 01:13:04 UTC

Maybe I should mention that this is 0.40-r1.

Comment 3 Harald van Dijk (RETIRED) gentoo-dev

2006-10-13 13:56:17 UTC

Thanks for the report, fixed in 0.40-r3 (without a revbump). I'm pretty sure portage only treats # that way by accident or chance though: bash behaves as ufed did. :)