From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: RFC: removing buildhistory support for flat versioned package info
Date: Fri, 22 Jun 2012 15:15:29 +0100 [thread overview]
Message-ID: <3297658.NN3oiPzfJJ@helios> (raw)
Hi all,
One feature carried over from packagehistory.bbclass into buildhistory.bbclass
was the ability for it to optionally output PE:PV-PR named package info files
and then create a "latest" symlink to the latest one, which was useful in the
absence of the integration with git which buildhistory now has. This can
currently be enabled by setting BUILDHISTORY_KEEP_VERSIONS to 1.
I suspect not many people even know this feature exists let alone use it, and
looking at the code it could be simplified a bit by not supporting it at all.
Are there any objections to removing it?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2012-06-22 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 14:15 Paul Eggleton [this message]
2012-06-22 14:53 ` RFC: removing buildhistory support for flat versioned package info Richard Purdie
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=3297658.NN3oiPzfJJ@helios \
--to=paul.eggleton@linux.intel.com \
--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