Re: [gentoo-dev] News Item: Changes in default VIDEO_CARDS

[Chí-Thanh Christopher Nguyễn]

Ciaran McCreesh schrieb:

On Thu, 29 Oct 2015 16:22:40 +0100
Chí-Thanh Christopher Nguyễn  wrote:

The previous time I wanted to post a news item with USE dependencies,
this was not possible because the Display-If-Installed dependency
atom had to conform to EAPI 0. But now that all profiles are EAPI 5
this is ok I hope.

It's not really clear what the EAPI for the news directory is...


I guess you are right, but as all package managers must now understand 
EAPI 5 dependency atoms, it is not likely that any will choke on it.
Besides, existing news items already use Display-If-Profile: to point to 
EAPI 5 profiles.

But I can ask the Council for clarification on the issue.


Best regards,
Chí-Thanh Christopher Nguyễn

Re: [gentoo-dev] News Item: Changes in default VIDEO_CARDS

[Ciaran McCreesh]

On Thu, 29 Oct 2015 17:13:29 +0100
Chí-Thanh Christopher Nguyễn  wrote:
> Ciaran McCreesh schrieb:
> > On Thu, 29 Oct 2015 16:22:40 +0100
> > Chí-Thanh Christopher Nguyễn  wrote:
> >> The previous time I wanted to post a news item with USE
> >> dependencies, this was not possible because the
> >> Display-If-Installed dependency atom had to conform to EAPI 0. But
> >> now that all profiles are EAPI 5 this is ok I hope.
> > It's not really clear what the EAPI for the news directory is...
> 
> I guess you are right, but as all package managers must now
> understand EAPI 5 dependency atoms, it is not likely that any will
> choke on it.

Well Portage won't, since it doesn't do input validation and will
pretty much allow you to use any EAPI's syntax anywhere. Paludis will
probably warn that you're using an EAPI 5 feature somewhere where EAPI
5 hasn't been declared, since everything that isn't explicitly a
particular EAPI is EAPI 0.

> Besides, existing news items already use
> Display-If-Profile: to point to EAPI 5 profiles.

That isn't how EAPIs work, conceptually. Whenever a PM does something
with a spec, it asks what the EAPI is in the context of that spec,
which in turn depends upon where that spec came from. A user using a
profile with EAPI 5 does not mean that every dep spec is treated as
being EAPI 5 -- the profile EAPI just applies to things from that
particular profiles directory. (And even if it did work the way you
think, users not using an EAPI 5 profile would still need to be able to
parse that news item...)

> But I can ask the Council for clarification on the issue.

Not so much a Council issue as a PMS one, but the trouble is that news
items slightly predate PMS and EAPIs.

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature

Re: [gentoo-dev] News Item: Changes in default VIDEO_CARDS

[Ciaran McCreesh]

On Thu, 29 Oct 2015 16:22:40 +0100
Chí-Thanh Christopher Nguyễn  wrote:
> The previous time I wanted to post a news item with USE dependencies, 
> this was not possible because the Display-If-Installed dependency
> atom had to conform to EAPI 0. But now that all profiles are EAPI 5
> this is ok I hope.

It's not really clear what the EAPI for the news directory is...

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature

[gentoo-dev] News Item: Changes in default VIDEO_CARDS

[Chí-Thanh Christopher Nguyễn]

x11 team plans to change the default VIDEO_CARDS on amd64/x86 per bug 
#561850.
Due to the USE dependencies of Display-If-Installed, this item will only 
be displayed on amd64 and x86 systems that have not overridden 
VIDEO_CARDS in make.conf. Other architectures will retain their 
VIDEO_CARDS and we will leave it to the respective arch teams to adjust 
this as desired.


The previous time I wanted to post a news item with USE dependencies, 
this was not possible because the Display-If-Installed dependency atom 
had to conform to EAPI 0. But now that all profiles are EAPI 5 this is 
ok I hope.


Title: Changes in default VIDEO_CARDS
Author: Chí-Thanh Christopher Nguyễn 
Content-Type: text/plain
Posted: 2015-10-30
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: 
x11-base/xorg-drivers[video_cards_dummy,video_cards_fbdev,video_cards_glint,video_cards_intel,video_cards_mach64,video_cards_mga,video_cards_nouveau,video_cards_nv,video_cards_r128,video_cards_radeon,video_cards_savage,video_cards_tdfx,video_cards_trident,video_cards_v4l,video_cards_vesa,video_cards_via,video_cards_vmware]


In order to better reflect the graphics chipsets present on modern
systems, the default VIDEO_CARDS setting has been changed to
"amdgpu fbdev intel nouveau radeon radeonsi vesa"

If your graphics chipset requires a different driver, and you have not set
VIDEO_CARDS in make.conf, it is advisable to do that now.

Re: [gentoo-dev] News Item: Changes in default VIDEO_CARDS

[Ulrich Mueller]

> On Thu, 29 Oct 2015, Ciaran McCreesh wrote:

> [...] but the trouble is that news items slightly predate PMS and
> EAPIs.

We could update GLEP 42 for a News-Item-Format 1.1 and allow EAPI 5
dependency specifications there.

Ulrich


pgpXPhwgCdiHV.pgp
Description: PGP signature

Re: [gentoo-dev] News Item: Changes in default VIDEO_CARDS

[Chí-Thanh Christopher Nguyễn]

Ulrich Mueller schrieb:

On Thu, 29 Oct 2015, Ciaran McCreesh wrote:

[...] but the trouble is that news items slightly predate PMS and
EAPIs.

We could update GLEP 42 for a News-Item-Format 1.1 and allow EAPI 5
dependency specifications there.

Ulrich


New-Item-Format 1.1 implies that it is backwards compatible if I read 
correctly?
If so, we would have to use some other identifier than 
"Display-If-Installed" because EAPI 5 dependency atoms are not a subset 
of EAPI 0 ones.


Maybe

News-Item-Format: 1.1
EAPI: 5
Display-If-Has_version: ...

where Display-If-Has_version is a dependency specification according to 
the given EAPI, and the package manager must ignore it if the EAPI is 
unsupported (thus will display the news item always, which will also 
happen with package managers that only support News-Item-Format 1.0).



Best regards,
Chí-Thanh Christopher Nguyễn

[gentoo-dev] News Item: Changes in default VIDEO_CARDS (v2)

[Chí-Thanh Christopher Nguyễn]

I changed the EAPI 5 dependency atom to EAPI 0 ones.

Title: Changes in default VIDEO_CARDS
Author: Chí-Thanh Christopher Nguyễn 
Content-Type: text/plain
Posted: 2015-10-30
Revision: 1
News-Item-Format: 1.0
Display-If-Keyword: amd64
Display-If-Keyword: x86
Display-If-Installed: x11-drivers/xf86-video-dummy
Display-If-Installed: x11-drivers/xf86-video-glint
Display-If-Installed: x11-drivers/xf86-video-mach64
Display-If-Installed: x11-drivers/xf86-video-mga
Display-If-Installed: x11-drivers/xf86-video-nv
Display-If-Installed: x11-drivers/xf86-video-r128
Display-If-Installed: x11-drivers/xf86-video-savage
Display-If-Installed: x11-drivers/xf86-video-tdfx
Display-If-Installed: x11-drivers/xf86-video-trident
Display-If-Installed: x11-drivers/xf86-video-v4l
Display-If-Installed: x11-drivers/xf86-video-via
Display-If-Installed: x11-drivers/xf86-video-vmware

In order to better reflect the graphics chipsets present on modern
systems, the default VIDEO_CARDS setting has been changed to
"amdgpu fbdev intel nouveau radeon radeonsi vesa"

If your graphics chipset requires a different driver, and you have not set
VIDEO_CARDS in make.conf, it is advisable to do that now.