Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] package_rpm.bbclass: Add srpm function
Date: Mon, 05 Mar 2012 12:04:55 -0500	[thread overview]
Message-ID: <1330967095.23796.4.camel@lenny> (raw)
In-Reply-To: <3fce8ebe8b9af73e91bd8baf397d1a9ac196171f.1330771239.git.xiaofeng.yan@windriver.com>

On Sat, 2012-03-03 at 18:54 +0800, Xiaofeng Yan wrote:
> From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
> 
> Add a new function to archive source, patches and logs to a source rpm
> package. Every source rpm package  will be deployed to
> ${DEPLOY}/sources/deploy-srpm.

What's the goal of this?  Just to be a "one file" collection of
sources?  Or do we actually expect people to build from this somehow?

If the intention is to eventually allow building, but it's not actually
used to build right now, it seems very likely to "bitrot" as the core
changes.





  reply	other threads:[~2012-03-05 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 10:53 [PATCH 0/3] Realize archiver.bbclass Xiaofeng Yan
2012-03-03 10:54 ` [PATCH 1/3] package_rpm.bbclass: Add srpm function Xiaofeng Yan
2012-03-05 17:04   ` Colin Walters [this message]
2012-03-03 10:54 ` [PATCH 2/3] archiver.bbclass: archive sources, patches, logs to tarball Xiaofeng Yan
2012-03-12 18:54   ` Mark Hatle
2012-03-13  7:29     ` Xiaofeng Yan
2012-03-03 10:54 ` [PATCH 3/3] archiver_configure.bbclass: configure the content for archiving package Xiaofeng Yan
2012-03-05 22:18   ` Saul Wold
2012-03-06 11:11     ` Xiaofeng Yan
2012-03-12 18:58   ` Mark Hatle
2012-03-13  6:48     ` Xiaofeng Yan
2012-03-05 22:28 ` [PATCH 0/3] Realize archiver.bbclass Saul Wold
2012-03-06 11:16   ` Xiaofeng Yan

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=1330967095.23796.4.camel@lenny \
    --to=walters@verbum.org \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox