678466 – Portage configuration files won't support bash string ops like ${VAR//SS/RS}

Bug 678466 - Portage configuration files won't support bash string ops like ${VAR//SS/RS}

Summary: Portage configuration files won't support bash string ops like ${VAR//SS/RS}

Status:	RESOLVED INVALID

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Configuration (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2019-02-21 07:31 UTC by Necktwi Ozfguah
Modified:	2019-02-27 20:43 UTC (History)
CC List:	0 users

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

Attachments
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 Necktwi Ozfguah 2019-02-21 07:31:44 UTC

Necktwi$ cat /etc/portage/env/O0
CFLAGS=${CFLAGS//-O2/-O0}
CXXFLAGS=$CFLAGS

Necktwi$ sudo emerge -av some_package
These are the packages that would be merged, in order:
Calculating dependencies -"/etc/portage/env/O0", line 2: unexpected EOF while looking for matching `}'

Comment 1 Georgy Yakovlev archtester

2019-02-27 20:22:28 UTC

you need to use bachrc env files, not package.env for that to work.

place contents of env/O0 file to /etc/portage/env/some-category/some_package

it should work from there.


https://dev.gentoo.org/~zmedico/portage/doc/ch01.html#config-bashrc-locations