From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: carrier.nicolas0@gmail.com
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] package/composer: new package
Date: Tue, 1 Aug 2023 23:11:07 +0200 [thread overview]
Message-ID: <20230801231107.78940dc0@windsurf> (raw)
In-Reply-To: <20230119132856.1801425-4-carrier.nicolas0@gmail.com>
Hello Nicolas,
On Thu, 19 Jan 2023 14:28:56 +0100
carrier.nicolas0@gmail.com wrote:
> From: Nicolas Carrier <carrier.nicolas0@gmail.com>
>
> composer describes itself as a dependency manager for PHP, it is used
> by projects such as CakePHP.
>
> Signed-off-by: Nicolas Carrier <carrier.nicolas0@gmail.com>
> ---
> package/composer/composer.hash | 3 +++
> package/composer/composer.mk | 31 +++++++++++++++++++++++++++++++
> 2 files changed, 34 insertions(+)
> create mode 100644 package/composer/composer.hash
> create mode 100644 package/composer/composer.mk
>
> diff --git a/package/composer/composer.hash b/package/composer/composer.hash
> new file mode 100644
> index 0000000000..512f4399a8
> --- /dev/null
> +++ b/package/composer/composer.hash
> @@ -0,0 +1,3 @@
> +# Locally computed hashes, not provided by upstream
Actually hashes are available at https://getcomposer.org/download/.
> +sha256 2021f0d52b446e0efe3c548cc058ab5671fa38cdbcf814e7911c7e9d71d61538 composer-2.0.8.phar
> +sha256 c8cce4b6b9729f264ffdf9296d505d63432497feeed1f586d1902b942197e024 LICENSE
> diff --git a/package/composer/composer.mk b/package/composer/composer.mk
> new file mode 100644
> index 0000000000..5ff5644d29
> --- /dev/null
> +++ b/package/composer/composer.mk
> @@ -0,0 +1,31 @@
> +################################################################################
> +#
> +# composer
> +#
> +################################################################################
> +
> +COMPOSER_VERSION = 2.0.8
I have bumped to 2.5.8, because at runtime 2.0.8 was spitting out a few
warnings about usage of PHP features that are deprecated/obsolete.
I've added a Config.in.host file so that this package can be enabled as
a host package from menuconfig.
And I now realize that I forgot to add a DEVELOPERS entry, so I will do
that now.
Applied with those changes!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-01 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:28 [Buildroot] [PATCH 0/3] new host-composer package patches series carrier.nicolas0
2023-01-19 13:28 ` [Buildroot] [PATCH 1/3] package/oniguruma/oniguruma.mk: add a host package carrier.nicolas0
2023-08-01 21:05 ` Thomas Petazzoni via buildroot
2023-01-19 13:28 ` [Buildroot] [PATCH 2/3] package/php/php.mk: add host-php carrier.nicolas0
2023-08-01 21:09 ` Thomas Petazzoni via buildroot
2023-01-19 13:28 ` [Buildroot] [PATCH 3/3] package/composer: new package carrier.nicolas0
2023-08-01 21:11 ` Thomas Petazzoni via buildroot [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=20230801231107.78940dc0@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=carrier.nicolas0@gmail.com \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.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