All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: debian packaging
Date: Tue, 10 Feb 2009 03:56:56 +0100	[thread overview]
Message-ID: <4990ECF8.2090605@gmx.net> (raw)
In-Reply-To: <59e7e6f90902091528o73d594c0y132770d49b1c9b61@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

Hi,

Mike Turquette schrieb:
> Hi all,
> 
> I'm trying to understand more about debian packaging in OE.  I know
> that OE can churn out dpkg's as a result, but does OE have a way to
> intelligently make use of source code that has a 'debian' directory
> complete with rules and all of that?
OE's debian packaging has nothing to do with the 'debian' directory.

> By 'intelligently' I mean can OE determine what DEPENDS and RDEPENDS
> should be, based on the dpkg control info and can it figure out what
> needs to go into staging?  I'm hoping for something analogous to
> autotools.bbclass which uses stuff in the source (instead of the
> recipe) to figure out much of the configuration and decision-making.
It is the other way round: By declaring you want .deb as output it will
take a package's RDEPENDS and many other information to create a deb's
control file.

The mamona project has some support for creating debian source packages,
too.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

  reply	other threads:[~2009-02-10  2:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 23:28 debian packaging Mike Turquette
2009-02-10  2:56 ` Robert Schuster [this message]
2009-02-13 20:52   ` Rodrigo Vivi
  -- strict thread matches above, loose matches on Subject: below --
2008-01-07 19:51 Debian Packaging Centurion Computer Technology (2005) Ltd
2008-01-07 22:00 ` Robert Millan
2008-01-07 22:06   ` Centurion Computer Technology (2005) Ltd
2008-01-07 22:13     ` Robert Millan
2008-01-07 22:26       ` Centurion Computer Technology (2005) Ltd
2008-01-08  1:03         ` Pavel Roskin
2008-01-08  9:11         ` Robert Millan

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=4990ECF8.2090605@gmx.net \
    --to=thebohemian@gmx.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.