You are not logged in.

#1 2017-05-28 18:36:26

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Are official packages built with [testing] enabled?

FS#54202 implies that [testing] is enabled on the build machine of at least [core]/linux.  I'm wondering what the official guidance is on this topic.  Is it a best practice to enable [testing] in the clean-chroot prior to building in general?  I seem to recall one of the packagers stating this in a FS from a few years ago but am unable to locate it.  Thanks.

Last edited by graysky (2017-05-28 20:15:43)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#2 2017-05-28 19:43:46

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,466

Re: Are official packages built with [testing] enabled?

Some are, some aren't. If it's being built to go directly into Extra, it's built against Extra. If it's built to go into testing/staging, it's built against testing/staging.

Offline

#3 2017-05-28 20:11:59

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Re: Are official packages built with [testing] enabled?

@Scimmia - That makes sense, thanks... but how is it determined?  For example, the linux package per that FS seems to have been built using GCC 7.1.x yet the kernel package is now in [core] and GCC is in [testing].

Last edited by graysky (2017-05-28 20:15:31)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#4 2017-05-28 22:55:37

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,466

Re: Are official packages built with [testing] enabled?

All Core packages go into Testing, so they're all built against Testing. The issue there is that the kernel moved from Testing to Core before GCC did, when they should have been moved as a set like is done with library rebuilds.

Offline

Board footer

Powered by FluxBB