Hi Javier,
Quoting Javier Serrano Polo (2018-01-31 00:18:01)
> Where should I report issues about the spec in the meantime?
build profiles came from the people who try to bootstrap Debian automatically.
We don't have a specific list for that task but an IRC channel at
#debian-bootstrap on OFTC.
Where should I report issues about the spec in the meantime?
smime.p7s
Description: S/MIME cryptographic signature
On Tue, Jul 18, 2017 at 10:33:06AM +0100, Simon McVittie wrote:
> I suspect stage1 might also still be useful for (possibly pre-emptively)
> breaking cycles involving build-time vs. runtime dependencies, like the one
> that historically existed between glib2.0 and dbus: it seems more
>
On Tue, 18 Jul 2017 at 09:06:23 +0200, Johannes Schauer wrote:
> It is not intended to completely forbid the "stage1" profile name. It is clear
> that it has its use for the initial cross-compiler bootstrap involving glibc,
> gcc and linux.
I suspect stage1 might also still be useful for
Quoting Ben Hutchings (2017-07-17 02:17:12)
> However, I can see it has changed since I last looked and now says that
> "stage1" has been deprecated. I don't understand why this is or how we're
> supposed to give this hint to bootstrapping tools now.
When package maintainers implement build
On Wed, 2017-06-21 at 16:01 -0700, Jonathan Nieder wrote:
[...]
> I'd like to restart this discussion. My understanding is that all the
> relevant infrastructure for build profiles is in place, so what's left
> is to add some text to policy documenting it.
>
> Is my understanding correct? Any
Hi Jonathan,
Quoting Jonathan Nieder (2017-06-22 01:01:10)
> > please document the new Build-Depends syntax and fields for build
> > profiles. The current write-up of the new syntax and fields for build
> > profiles lives at https://wiki.debian.org/BuildProfileSpec
> >
> > Please note, that the
Hi,
Johannes Schauer wrote:
> please document the new Build-Depends syntax and fields for build
> profiles. The current write-up of the new syntax and fields for build
> profiles lives at https://wiki.debian.org/BuildProfileSpec
>
> Please note, that the new Build-Depends syntax element is
On Wed, 13 Jul 2016 07:10:16 +0200 Johannes Schauer wrote:
> because of technical reasons?
Administrative reasons (https://bugs.debian.org/831059). I will have to
open a bug against dpkg for this issue.
(I have worked around the error in my mail server.)
smime.p7s
Hi,
Quoting Javier Serrano Polo (2016-07-13 01:04:43)
> Sorry, I missed your message.
>
> > I'm removing #757760 from the recipients because that bug should
> > contain a discussion about the implementation of the current build
> > profile spec and should not be a discussion platform for further
Sorry, I missed your message.
> I'm removing #757760 from the recipients because that bug should
> contain a discussion about the implementation of the current build
> profile spec and should not be a discussion platform for further
> additions or changes to the spec. Lets use debian-dpkg@ to
El dg 10 de 07 de 2016 a les 19:25 +0200, Javier Serrano Polo va
escriure:
> For instance, the linux source
> package should have a way to build only linux-image-4.6.0-1-686 (profile
> pkg.linux.686)
Current linux package already uses build profiles. It looks like the
specification works better
On Sat, 09 Jul 2016 23:56:03 +0200 Johannes Schauer
wrote:
> I'm CC-ing debian-dpkg@.
I cannot CC lists.debian.org. You will not see my messages in
https://lists.debian.org/debian-policy/2016/07/threads.html .
> I suspect you want to express "this package has to be built when
Hi Javier,
Quoting Javier Serrano Polo (2016-07-09 21:40:35)
> Where is this feature discussed?
we talk about it on debian-dpkg@, debian-cross@ and occasionally I guess on
deity@. Some discussion about build profiles also happens in IRC on
#debian-bootstrap, #debian-dpkg and sometimes
Where is this feature discussed?
Could the token "<>" indicate "no build profiles"? That would allow:
Build-Profiles: <>
I gather that the Built-For-Profiles field is written to DEBIAN/control
when DEB_BUILD_PROFILES is not empty. Could a profile "subset" avoid
this field? Example:
Package: debian-policy
Severity: wishlist
Hi,
please document the new Build-Depends syntax and fields for build
profiles. The current write-up of the new syntax and fields for build
profiles lives at https://wiki.debian.org/BuildProfileSpec
Please note, that the new Build-Depends syntax element
16 matches
Mail list logo