public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/5] Unify work space for packages
Date: Mon, 11 Sep 2017 11:19:52 +0300	[thread overview]
Message-ID: <c267c6bd-7197-c229-6fef-f53f8da86f22@ilbers.de> (raw)
In-Reply-To: <20170911100003.0c3d4ce7@md1em3qc>



On 09/11/2017 11:00 AM, Henning Schild wrote:
> Am Mon, 11 Sep 2017 10:36:02 +0300
> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> 
>> On 09/08/2017 07:15 PM, Henning Schild wrote:
>>> Am Fri, 8 Sep 2017 19:10:37 +0300
>>> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>>>    
>>>> On 09/08/2017 07:06 PM, Henning Schild wrote:
>>>>> Looks good, except for the minor things i just found.
>>>>
>>>> Thanks for the quick response. Will fix according to your
>>>> comments.
>>>
>>> You are welcome.
>>>    
>>>> Could you please re-base your series on top of this?
>>>
>>> Sure. But i would prefer to do this rebase together with addressing
>>> issues found in the review. So please provide reviews to all
>>> patches, catch up on the nameing discussions etc. and give me a
>>> green light by replying here again.
>>>    
>>
>> There is nothing more from me. Only one possible topic - names of the
>> classes. Eventually we will have at least three pipelines:
>>
>>    - Build package in chroot (current Isar flow).
>>    - Pack custom files (your proposal).
>>    - Cross-compilation for custom packages.
>>
>> So, probably we can use following names (respectively):
>>
>>    - dpkg-native.bbclass
> 
> Would that be the current dpkg.bbclass? In that case i do not like the
> name since we cross-compile with it as well.
> 
>>    - dpkg-pack.bbclass
>>    - dpkg-cross.bbclass
> 
> If we ever decide to add custom building i think it would go into the
> class my patches introduce.
> 
> So i think we will have a debian and a custom way of building debian > packages, hence the names currently suggested. Maybe best discuss this
> in the thread already opened for that.

Ok.

> 
> Henning
>   
>> Alex
>>
>>>>>
>>>>> Am Fri, 8 Sep 2017 18:56:01 +0300
>>>>> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>>>>>       
>>>>>> Hi all,
>>>>>>
>>>>>> this series does the following:
>>>>>>     - Simplifies folders structure for multiconfig.
>>>>>>     - Unifies work space for packages.
>>>>>>     - Use unified canonical names for  build artifacts.
>>>>>>
>>>>>> The overal build tree with multiconfig looks like the following:
>>>>>> $ ls -1 tmp/work/
>>>>>>     debian-jessie-amd64
>>>>>>     debian-jessie-armhf
>>>>>>     debian-jessie-i386
>>>>>>     debian-stretch-amd64
>>>>>>     debian-stretch-armhf
>>>>>>     debian-stretch-i386
>>>>>>     debian-wheezy-armhf
>>>>>>     raspbian-jessie-armhf
>>>>>>
>>>>>> Package workdir looks now like the following:
>>>>>> $ ls -1 tmp/work/debian-jessie-amd64/hello-0.1+g7f35942-1-r0/
>>>>>> git
>>>>>> hello_0.1+g7f35942-1_amd64.changes
>>>>>> hello_0.1+g7f35942-1_amd64.deb
>>>>>> hello_0.1+g7f35942-1.dsc
>>>>>> hello_0.1+g7f35942-1.tar.gz
>>>>>> temp
>>>>>>
>>>>>> Changes since v1:
>>>>>>     - Split first patch into pieces.
>>>>>>     - Use variable in multistrap config.
>>>>>>     - Rename ext4 image to unified cacnonical name (patch 4).
>>>>>>
>>>>>> With best regards,
>>>>>> Alex
>>>>>>
>>>>>> Alexander Smirnov (5):
>>>>>>      image: Unify path to image rootfs
>>>>>>      isar: Change build folders tree
>>>>>>      stamps: Name stamps canonicaly and unified
>>>>>>      image: Name image canonicaly and unified
>>>>>>      class/dpkg: Unify workplace for packages
>>>>>>
>>>>>>     meta-isar/classes/rpi-sdimg.bbclass              |  2 +-
>>>>>>     meta-isar/recipes-core/images/isar-image-base.bb | 18
>>>>>> ++++++++----------
>>>>>> meta/classes/dpkg.bbclass                        | 15
>>>>>> +++++++++------ meta/classes/ext4-img.bbclass
>>>>>> | 12 ++++++------
>>>>>> meta/classes/image.bbclass                       | 11
>>>>>> ++++++----- meta/conf/isar-bitbake.conf                      | 5
>>>>>> ++++- meta/recipes-devtools/buildchroot/buildchroot.bb |  8
>>>>>> ++++---- scripts/start_vm                                 |  2
>>>>>> +- 8 files changed, 39 insertions(+), 34 deletions(-)
>>>>>       
>>>>   
>>>    
>>
> 

-- 
With best regards,
Alexander Smirnov

ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov

      reply	other threads:[~2017-09-11  8:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 15:56 Alexander Smirnov
2017-09-08 15:56 ` [PATCH v2 1/5] image: Unify path to image rootfs Alexander Smirnov
2017-09-08 16:00   ` Henning Schild
2017-09-08 15:56 ` [PATCH v2 2/5] isar: Change build folders tree Alexander Smirnov
2017-09-08 16:04   ` Henning Schild
2017-09-08 15:56 ` [PATCH v2 3/5] stamps: Name stamps canonicaly and unified Alexander Smirnov
2017-09-08 15:56 ` [PATCH v2 4/5] image: Name image " Alexander Smirnov
2017-09-08 15:56 ` [PATCH v2 5/5] class/dpkg: Unify workplace for packages Alexander Smirnov
2017-09-11 16:47   ` Henning Schild
2017-09-11 18:10     ` Alexander Smirnov
2017-09-08 16:06 ` [PATCH v2 0/5] Unify work space " Henning Schild
2017-09-08 16:10   ` Alexander Smirnov
2017-09-08 16:12     ` Alexander Smirnov
2017-09-08 16:15     ` Henning Schild
2017-09-11  7:36       ` Alexander Smirnov
2017-09-11  8:00         ` Henning Schild
2017-09-11  8:19           ` Alexander Smirnov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c267c6bd-7197-c229-6fef-f53f8da86f22@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox