All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Sargent <butters@station51.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenLDAP 2.4.21. doesn't create packages
Date: Sun, 04 Jul 2010 15:55:17 +0200	[thread overview]
Message-ID: <4C3092C5.5060606@station51.net> (raw)
In-Reply-To: <4C2CE2E6.3050708@station51.net>



On 7/1/2010 8:48 PM, Bill Sargent wrote:
>  Hello,
>
> I'm trying to add the openldap 2.4.21 recipe to my bootable image, and 
> it doesn't seem to be creating the packages. It installs only the libs 
> and no binaries (slapd etc..) ... I looked at the recipe and it seems 
> it should be creating some bin package as well as base etc... but I 
> haven't seen any in my packages directories.
>
> Can someone explain to me what is wrong? Is there a problem with the 
> openldap recipe?
>
> Thanks
> Bill

Well I wrote this the other day and as usual, nobody responded. I 
finally got it to spit out libldap-2.40*.ipk with the slapd etc... 
however, adding

libldap-2.4-slapd
and
libldap-2.4-bin

to my IMAGE_INSTALL variable doesn't seem to work. Can someone explain 
to me, the correct way to install a full working openldap server and 
utilities into an image?

As much documentation as there is for this, apparently we need a list of 
installable packages as well since the filenames don't exactly always 
mean that it's a package name thats installable.  If there is one, I've 
missed it I think :)

Thanks,
Bill





  reply	other threads:[~2010-07-04 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 18:48 OpenLDAP 2.4.21. doesn't create packages Bill Sargent
2010-07-04 13:55 ` Bill Sargent [this message]
2010-07-04 17:58   ` Khem Raj
2010-07-04 21:31     ` Bill Sargent
2010-07-05  0:33       ` Khem Raj
2010-07-06  9:51         ` Bill Sargent

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=4C3092C5.5060606@station51.net \
    --to=butters@station51.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.