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] [pull request] Pull request for branch for-2012.08/systemd
Date: Thu, 9 Aug 2012 11:45:26 +0200	[thread overview]
Message-ID: <20120809114526.742e2e38@skate> (raw)
In-Reply-To: <CADiAo4LsWUje0=p0QvJqgK_tAiT1XtsSs9J9qFmHswSYvzSSew@mail.gmail.com>

Hello Dmitry,

Le Mon, 6 Aug 2012 11:14:50 -0400,
Dmitry Golubovsky <golubovsky@gmail.com> a ?crit :

> While still a bit away from this project (and will resume work on
> patches for linux-pam as soon as I can), I think I can also contribute
> into the systemd discussion:
> 
> Thomas Petazzoni wrote:
> 
> > Also, it would be good to investigate the newer versions of
> > systemd. If I remember correctly, they integrate udev directly, but
> > is it possible to still have udev separately? This of course will
> > not be for 2012.08, but it would be nice to continue to integrate
> > those technologies into Buildroot.
> 
> My latest systemd patches are for version 186 (don't worry about 185
> in patches themselves: this part of the path is discarded anyway - and
> now there is 187). See here:
> 
> https://gitorious.org/lfa/myroot/trees/master/systemd-pam
> 
> Code layout changed considerably in this new version series (185 and
> up).

This repository is unfortunately a bit unusable: it isn't a fork from
the original Buildroot repository. Why did you create a new repository
that contains just the source code of a package? You should instead
clone the original Buildroot repository, create a branch, and push it
on Gitorious.

Also, your work on PAM+systemd should not be a new systemd-pam package:
it should be integrated (probably with configuration options) into the
existing systemd package.

> Yes, they integrated udev together with systemd, and I do not see any
> option to build udev separately from their source tree: there isn't
> even such repo as udev at freedesktop.
> 
> Now I see that Buildroot gets udev from different source. Could these
> be just two mutually exclusive config options: either to build udev
> with systemd, or udev standalone (and disable building of systemd)?

Now that udev is part of the systemd sources, do they publish new
udev-only release tarballs? I guess not. If I'm correct, then we should
simply remove the 'udev' package, and implement a mechanism to allow
the systemd package to install only udev, or udev+systemd.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-08-09  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 15:14 [Buildroot] [pull request] Pull request for branch for-2012.08/systemd Dmitry Golubovsky
2012-08-09  9:45 ` Thomas Petazzoni [this message]
2012-08-09 14:29   ` Dmitry Golubovsky
  -- strict thread matches above, loose matches on Subject: below --
2012-07-28  7:21 Maxime Ripard
2012-07-28  7:30 ` Maxime Ripard
2012-07-30 21:21 ` Thomas Petazzoni
2012-08-01  9:18   ` Maxime Ripard
2012-05-25 12:11 Maxime Ripard

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=20120809114526.742e2e38@skate \
    --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