Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Howto handle fork of an existing package
Date: Fri, 4 Aug 2017 16:41:45 +0200	[thread overview]
Message-ID: <20170804164145.21595c6d@windsurf.lan> (raw)
In-Reply-To: <6947b9e4-bf6e-ace7-c8c9-e440a494e225@gmail.com>

Hello,

On Fri, 4 Aug 2017 14:21:26 +0200, Atilla Filiz wrote:

> I have made a package of Wiring Pi for Lemaker boards Banana Pi and 
> Banana Pro. Since this is a fork from an older version, the site, teh 
> versioning, the patches etc are all different. I would like to ask, 
> whoat would be the best way to merge this package properly. Either
> 
> 1. Make it a completely new package, like wiringpi-lemaker and make it 
> depend on !BR2_PACKAGE_WIRINGPI and vice versa. Easiest way.
> 
> 2. Turn wiringpi into a subtree, with a radio button for board 
> selection: Raspberry Pi, Banana Pi, Banana Pro and enable teh proper 
> package. Raspberry Pi being the default option. Slightly intrusive way.
> 
> 3. Have one wiringpi to rule them all. Make the board selection as a 
> mere set of parameters. Make a bit more complicated wirinpi.mk that 
> selects correct site, version, patch directory etc depending on a bunch 
> of defined flags. Possibly unnecessarily complicated.

4. Contribute to the official wiringpi project instead of doing a fork,
so that a single project supports multiple platforms.

I think I have a preference for option (4). If not possible, option (3)
will be acceptable, but not as nice :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-08-04 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 12:21 [Buildroot] Howto handle fork of an existing package Atilla Filiz
2017-08-04 14:41 ` Thomas Petazzoni [this message]
2017-08-04 16:41   ` Arnout Vandecappelle
2017-08-04 17:03     ` Atilla Filiz

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=20170804164145.21595c6d@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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