There seems to be a new use flag 'acl', default is set to true, and it makes
sys-apps/acl a dependency for builing cups

Only problem is that the version of acl (2.2.45) needed by stable cups doesn't build. I get the
following error:
include/builddefs:59: *** missing separator. Stop.

For now, I've added '-acl' to the use flags in my /etc/make.conf.
Any downside to doing that?

On Sat, 19 Jul 2008 10:51:52 -0500, AZ Nomad <aznomad.3 at (no spam) PremoveOBthisOX.COM> wrote:
There seems to be a new use flag 'acl', default is set to true, and it makes
sys-apps/acl a dependency for builing cups

Only problem is that the version of acl (2.2.45) needed by stable cups doesn't build. I get the
following error:
include/builddefs:59: *** missing separator. Stop.

For now, I've added '-acl' to the use flags in my /etc/make.conf.
Any downside to doing that?

That use flag might have gotten it's default value of being set as a result
of my switching profiles. I got a message that my profile was obsolete so I
updated it to amd64/2008.0/developer

AZ Nomad wrote:
On Sat, 19 Jul 2008 10:51:52 -0500, AZ Nomad <aznomad.3 at (no spam) PremoveOBthisOX.COM> wrote:
There seems to be a new use flag 'acl', default is set to true, and it makes
sys-apps/acl a dependency for builing cups

Only problem is that the version of acl (2.2.45) needed by stable cups doesn't build. I get the
following error:
include/builddefs:59: *** missing separator. Stop.

For now, I've added '-acl' to the use flags in my /etc/make.conf.
Any downside to doing that?

That use flag might have gotten it's default value of being set as a result
of my switching profiles. I got a message that my profile was obsolete so I
updated it to amd64/2008.0/developer

That is a profile that may not be as good for an end user

Use the default

/usr/portage/profiles/default/linux/amd64/2008.0
doesn't seem to be a valid profile on my system.

or

/usr/portage/profiles/default/linux/amd64/2008.0/desktop
OK. I set to that one, but acl is still set, can't be build due to the

There seems to be a new use flag 'acl', default is set to true, and
it makes
sys-apps/acl a dependency for builing cups

Only problem is that the version of acl (2.2.45) needed by stable
cups doesn't build. I get the following error:
include/builddefs:59: *** missing separator. Stop.

For now, I've added '-acl' to the use flags in my /etc/make.conf.
Any downside to doing that?

AZ Nomad <aznomad.3 at (no spam) PremoveOBthisOX.COM> wrote:
There seems to be a new use flag 'acl', default is set to true, and
it makes
sys-apps/acl a dependency for builing cups

Only problem is that the version of acl (2.2.45) needed by stable
cups doesn't build. I get the following error:
include/builddefs:59: *** missing separator. Stop.

For now, I've added '-acl' to the use flags in my /etc/make.conf.
Any downside to doing that?

Well, you won't get POSIX acl (access control lists), which allow for each
file and directory having different permissions for different users and
groups. The perhaps most used feature of this is for allowing non-root
processes to give access to specified users, without requiring special
groups to be set up.
The downside to removing -acl would be that any existing acls that apps
might rely on would be ignored, leaving the file system in an inconsistent
state, especially if you later add acls again. But in your case, you
haven't had acls working in the first place, so that shouldn't be an issue.

Anyhow, I would look at why you get the compile error first. 2.2.45 should
be stable, so the problem might be elsewhere. autoconf, perhaps?
Done an "emerge --pretend --prune" lately, and removed what isn't needed,
followed by a re-emerge of the latest version?

On Sat, 19 Jul 2008 18:44:55 +0200, J.O. Aho <user at (no spam) example.net> wrote:

Use the default
/usr/portage/profiles/default/linux/amd64/2008.0
doesn't seem to be a valid profile on my system.
!!! Error: default/linux/amd64/2008.0 is not a valid profile for amd64

On Sat, 19 Jul 2008 13:45:18 -0400, Arthur Hagen <art at (no spam) broomstick.com
wrote:
Done an "emerge --pretend --prune" lately, and removed what isn't
needed, followed by a re-emerge of the latest version?

I'll try that. I can't right now as my use flags have changed.
I got this error:
"Have you forgotten to run emerge --update --newuse --deep world
prior to prune? It may be necessary to manually uninstall
packages that no longer exist in the portage tree since it may
not be possible to satisfy their dependencies. Also, be aware of
the --with-bdeps option that is documented"

/usr/portage/profiles/default/linux/amd64/2008.0
doesn't seem to be a valid profile on my system.
!!! Error: default/linux/amd64/2008.0 is not a valid profile for amd64

/usr/portage/profiles/default/linux/amd64/2008.0/desktop
OK. I set to that one,

but acl is still set, can't be build due to the
previously mentioned build error and is a requirement of cups.

No problem; I'll put "-acm" back in /etc/make.conf:USE

On Sat, 19 Jul 2008 18:44:55 +0200, J.O. Aho <user at (no spam) example.net> wrote:
....

No problem; I'll put "-acm" back in /etc/make.conf:USE

On Sat, 19 Jul 2008 12:22:50 -0500, AZ Nomad <aznomad.3 at (no spam) PremoveOBthisOX.COM> wrote:
On Sat, 19 Jul 2008 18:44:55 +0200, J.O. Aho <user at (no spam) example.net> wrote:
...

No problem; I'll put "-acm" back in /etc/make.conf:USE


Now the main error with sys-apps/acl-2.2.45 is:
* Sorry, but acl does not support the LINGUAs: en

AZ Nomad wrote:
On Sat, 19 Jul 2008 12:22:50 -0500, AZ Nomad <aznomad.3 at (no spam) PremoveOBthisOX.COM> wrote:
On Sat, 19 Jul 2008 18:44:55 +0200, J.O. Aho <user at (no spam) example.net> wrote:
...

No problem; I'll put "-acm" back in /etc/make.conf:USE


Now the main error with sys-apps/acl-2.2.45 is:
* Sorry, but acl does not support the LINGUAs: en

That should be just a warning. And pretty normal too. That's the
reason I have LINGUAS="en_US en" in make conf; some programs recognize
"en" while others see only "en_US".

Anyway, that message should not be an error but rather a warning.