Hi, On Mon, 27 Sep 2010, Russ Allbery wrote: > > Well, I don't make it a requirement to implement it right now and the > > Build-Features code can certainly start with just the build-arch > > stuff. But I want to make sure we gave it enough thought so that it's > > not problematic later on to extend it to other similar but slightly > > different needs. > > Is there anything about the syntax: > > Build-Features: build-arch > > to indicate that the package supports build-arch/build-indep targets (I > don't see any point in supporting one and not the other) that you think > would cause a problem for future expansion? I'd add a note that if there > are other build features, they'll be a comma-separated list of similar > keywords.
Well, we specified DEB_BUILD_OPTIONS space separated because build flags frequently embed commas. Shall we not take the same decision preemptively here? Also if we want to have lists as values for some "features" — like "disable-hardening=pie,relro" — we'd be better with using space separator. Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100930195603.ga19...@rivendell.home.ouaza.com
