All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Oudinet <johan.oudinet@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] ejabberd: new package
Date: Thu, 16 Oct 2014 14:38:12 +0200	[thread overview]
Message-ID: <CAJtjsKZC=Fi4ND7HX+YEEyGrNivu+6RduYnQ08FmVWU+NAiYqA@mail.gmail.com> (raw)
In-Reply-To: <20141011162152.GA4254@free.fr>

Hi Yann, all,

On Sat, Oct 11, 2014 at 6:21 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>
> We've been discussing this ejabberd patch during the current Developpers
> Day in D?sseldorf.
>
> Given the current issues that ewre noticed with building ejabberd, we
> decided to mark the patch as Rejected in patchwork.
>
> This means that we rejected that very specific patch, *not* that we
> decided not to have ejabberd. But before it gets included, all the
> issues must be fixed first, especially the build-time downloading of
> dependencies, as well as all the remarks that were made by Thomas and I.

Sure, it makes sense to me as well. As I said in a previous mail, I
did fix my patch to include your remarks, but two:
1. Fix ejabberd build system to not download dependencies at build time.
2. Avoid to use a fix UID and GID for ejabberd user.

I don't know if I should republish the patch before fixing these two issues.
I'd like your help on both of them.

** Fix ejabberd build system
** ===================
The only solution i see is to create a buildroot package for every
ejabberd dependency, listed in rebar.config.script :
esip, goldrush, lager, p1_cache_tab, p1_iconv, p1_stringprep, p1_stun,
p1_tls, p1_utils, p1_xml, p1_yaml, p1_zlib, xmlrpc
Then, modify ejabberd package to not use rebar at all, or at least to
not call rebar get-deps. Thus, if I remove deps from the `all'
makefile rule and deps/.build from the `src' rule dependency, it might
work.

Do you have a better idea?

** Avoid to use a fix UID and GID for ejabberd user
** ===================================

I still don't know how I could set the correct permissions to ejabberd
files in <PKG>_PERMISSIONS if I set -1 for UID and GID in <PKG>_USERS

Best regards,
-- 
Johan

  reply	other threads:[~2014-10-16 12:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 12:33 [Buildroot] [PATCH v3] ejabberd: new package Johan Oudinet
2014-07-18 21:35 ` Yann E. MORIN
2014-07-18 23:58   ` Johan Oudinet
2014-07-19  9:17     ` Yann E. MORIN
2014-07-20  9:33 ` Thomas Petazzoni
2014-08-06 10:30   ` Johan Oudinet
2014-08-06 19:40     ` Yann E. MORIN
2014-08-06 20:23 ` Yann E. MORIN
2014-08-11  9:36   ` Johan Oudinet
2014-08-11 10:07     ` Johan Oudinet
2014-08-11 10:13       ` Yann E. MORIN
2014-08-11 10:33     ` Yann E. MORIN
2014-08-11 10:50       ` Yann E. MORIN
2014-08-13 18:48         ` Frank Hunleth
2014-08-13 19:51           ` Yann E. MORIN
2014-08-13 20:44           ` Yann E. MORIN
2014-08-13 21:23             ` Frank Hunleth
2014-08-13 21:49               ` Yann E. MORIN
2014-08-13 22:18                 ` Yann E. MORIN
2014-08-14 12:40                   ` Frank Hunleth
2014-08-14 22:36                     ` Yann E. MORIN
2014-08-11 13:13       ` Johan Oudinet
2014-08-12 15:13         ` Yann E. MORIN
2014-10-11 16:21 ` Yann E. MORIN
2014-10-16 12:38   ` Johan Oudinet [this message]
2014-10-17 20:18     ` Yann E. MORIN
2014-10-17 23:06     ` Arnout Vandecappelle
2014-10-18 10:00       ` Yann E. MORIN
2014-10-18 10:31         ` Johan Oudinet
2014-10-27 14:42           ` Johan Oudinet
2014-10-27 14:47             ` Thomas Petazzoni

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='CAJtjsKZC=Fi4ND7HX+YEEyGrNivu+6RduYnQ08FmVWU+NAiYqA@mail.gmail.com' \
    --to=johan.oudinet@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.