- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Mar 2023 08:50:53 +0000
- To: public-css-archive@w3.org
> > Would it be appropriate to get a WG resolution on this, effectively approving that WPT drops support for the old CSS build system requirements? > > @foolip Can you define what this means exactly? There's the change itself and there's the CSSWG buy-in. The proposed change is https://github.com/web-platform-tests/wpt/pull/38976, and the part that benefits the WPT project is removing the CSS-specific lints that are about directory structure and file naming, most notably the one requiring globally unique file names. This will make css/ follow the same naming rules as the rest of WPT. Then there's the build system in css/tools/ that builds the directories ending with `_dev` that end(ed) up on https://test.csswg.org/. I just confirmed that it does run to completion locally: ``` sudo apt-get install python2.7 python2.7-dev PYTHON=python2.7 ./build.sh ``` This code isn't run in WPT CI and doesn't do any harm, but when it's not running anywhere any longer we'd like to remove it. Agenda+ and a resolution would be one way to ensure all the right people are aware of the issue, but the mechanism isn't important, I just don't want anyone to be surprised/unhappy if we make the change. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6896#issuecomment-1482451572 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 March 2023 08:50:55 UTC