Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Luca Vercelli <luca.vercelli.to@gmail.com>
Newsgroups: linux.debian.maint.java
Subject: Re: plans for eclipse luna in debian
Date: Tue, 16 Feb 2016 21:10:01 +0100
Message-ID: <r2U6B-4e2-1@gated-at.bofh.it>
References: <pbaVk-2ca-15@gated-at.bofh.it> <qhJ1L-7NG-11@gated-at.bofh.it> <qhJEu-l4-19@gated-at.bofh.it> <qkzpg-6HT-25@gated-at.bofh.it> <qkBho-14t-15@gated-at.bofh.it> <qkYnD-17l-3@gated-at.bofh.it> <qlCO6-1qN-13@gated-at.bofh.it> <qlIAa-1CH-5@gated-at.bofh.it> <qtmj7-kz-9@gated-at.bofh.it> <qtmj7-kz-7@gated-at.bofh.it> <qFmdI-5c9-7@gated-at.bofh.it> <qFmdI-5c9-9@gated-at.bofh.it> <qFmdI-5c9-11@gated-at.bofh.it> <qFmdI-5c9-5@gated-at.bofh.it> <qOhHP-7YB-3@gated-at.bofh.it> <qOiaS-8bd-33@gated-at.bofh.it> <qOjTk-SP-15@gated-at.bofh.it> <qOkFI-1wu-7@gated-at.bofh.it> <qRtt7-1gu-5@gated-at.bofh.it> <r2JXA-5TU-33@gated-at.bofh.it> <r2JXB-5TU-49@gated-at.bofh.it> <r2RLs-2yT-19@gated-at.bofh.it> <r2TWX-3TM-21@gated-at.bofh.it>
Old-Return-Path: <luca.vercelli.to@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Approved: robomod@news.nic.it
Lines: 34
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:8873

Can you have different patches to source code, according to different
profiles?
If so, then probably it's possible to do what you say.


Il 16/02/2016 20:57, Thorsten Glaser ha scritto:
> On Tue, 16 Feb 2016, Luca Vercelli wrote:
>
>> I don't know what are "build profiles" :(
> Then ask before thinking ;-)
>
>> however I dont' think so,
> Mayyyyybe. With build profiles, you have something similar to
> Maven profiles in that you can:
>
> • have different Build-Depends (on the debian/control side)
> • generate less and/or different binary packages
> • have different code (in debian/rules you can switch on a new
>   environment variable DEB_BUILD_PROFILES so you can use two
>   (partially or even completely) different recipes for building
>   while using the same source
>
> This is intended especially for bootstrapping and cross-builds:
> you first compile with the bootstrap profile enabled, then do
> whatever is needed to get the full profile working, then build
> it without the bootstrap profile, superseding the bootstrapping
> upload. (It’s intended that way, to be used to break dependency
> cycles and bootstrap, not to flavourise packages inside just one
> distribution… though I wish I could have a distro-specific default
> profile so there were no delta between Debian and the-derivate-
> which-cannot-be-named-from-Canonical any more, for one of mine.)
>
> bye,
> //mirabilos