> "S" == Samuel Thibault writes:
S> Roland Fehrenbacher, le mer. 30 sept. 2020 20:47:58 +0200, a
S> ecrit:
>> Is the only solution here then really to have two source packages
>> with exactly the same upstream source and only a difference in
>> the way the binaries are
On Wed, Sep 30, 2020 at 10:11 PM Richard Laager wrote:
> I would expect that:
>
> 1. main builds include main repositories
> 2. contrib builds include main, contrib, & non-free repositories
> 3. non-free builds include main, contrib, & non-free repositories
AFAICT, we don't use separate chroots
On 9/30/20 4:45 PM, Paul Wise wrote:
> The
> official buildds, for packages in main, seem to include contrib but
> not non-free binary packages in the chroot's apt sources.list files.
> Both contrib and non-free source packages are available in the chroots
> apt sources.list files. This appears to
On Wed, Sep 30, 2020 at 8:48 PM Philipp Kern wrote:
> Somewhat ironically not depending on anything but main is also true for
> non-free and contrib. (At least when you want it to be built by the
> official builders.)
That doesn't appear to be the current situation on the buildds. The
official
On 30.09.20 22:45, Josh Triplett wrote:
> [Accidentally sent this early before it was finished.]
>
> Roland Fehrenbacher wrote:
>>> "S" == Sven Joachim writes:
>> S> In addition, the packages in *main*
>> S>
>> S> * must not require or recommend a package outside of *main* for
Roland Fehrenbacher wrote:
> > "S" == Sven Joachim writes:
> S> In addition, the packages in *main*
> S>
> S> * must not require or recommend a package outside of *main* for
> S> compilation or execution (thus, the package must not declare a "Pre-
> S> Depends",
[Accidentally sent this early before it was finished.]
Roland Fehrenbacher wrote:
> > "S" == Sven Joachim writes:
> S> In addition, the packages in *main*
> S>
> S> * must not require or recommend a package outside of *main* for
> S> compilation or execution (thus, the
Roland Fehrenbacher writes:
>> "S" == Sven Joachim writes:
> S> No, see Policy ยง2.2.1:
> S> In addition, the packages in *main*
> S>
> S> * must not require or recommend a package outside of *main* for
> S> compilation or execution (thus, the package must not declare
Quoting Roland Fehrenbacher (2020-09-30 20:47:58)
> > "S" == Sven Joachim writes:
>
> Hi Sven and Adam,
>
> many thanks for your quick answers.
>
> S> On 2020-09-30 19:31 +0200, Roland Fehrenbacher wrote:
> >> Hi,
> >>
> >> a quick question to the list, since I didn't find
Roland Fehrenbacher, le mer. 30 sept. 2020 20:47:58 +0200, a ecrit:
>Is the only solution here then really to have two source packages
> with exactly the same upstream source and only a difference in
> the way the binaries are built and what they depend upon?
That's what I do with starpu and
> "S" == Sven Joachim writes:
Hi Sven and Adam,
many thanks for your quick answers.
S> On 2020-09-30 19:31 +0200, Roland Fehrenbacher wrote:
>> Hi,
>>
>> a quick question to the list, since I didn't find an answer after
>> a significant time of searching:
>>
On Wed, 2020-09-30 at 19:31 +0200, Roland Fehrenbacher wrote:
> a quick question to the list, since I didn't find an answer after a
> significant time of searching:
>
> Is it allowed to have a source package with a build dependency on a
> pkg in non-free (in this particular case
On 2020-09-30 19:31 +0200, Roland Fehrenbacher wrote:
> Hi,
>
> a quick question to the list, since I didn't find an answer after a
> significant time of searching:
>
> Is it allowed to have a source package with a build dependency on a pkg in
> non-free (in this particular case
13 matches
Mail list logo