From: Martin Jansa <martin.jansa@gmail.com>
To: Laszlo Papp <lpapp@kde.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Why is "bitbake core-image-minimal" building gtk docs?
Date: Wed, 21 Aug 2013 13:04:01 +0200 [thread overview]
Message-ID: <20130821110401.GG522@jama> (raw)
In-Reply-To: <CAOMwXhP6awmXzW2Sm0OMKyrWBFtQRje1CkL3yWtvzdU6fvd1bw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]
On Wed, Aug 21, 2013 at 11:31:53AM +0100, Laszlo Papp wrote:
> On Wed, Aug 21, 2013 at 11:26 AM, Burton, Ross <ross.burton@intel.com>wrote:
>
> > On 21 August 2013 11:24, Laszlo Papp <lpapp@kde.org> wrote:
> >
> >> I am not saying to fix gtk-doc-stub only. I am saying fix the nastiness
> >> of using git repositories for released and supposedly stable versions. I do
> >> not see why tarball would not be enough for those to work off-hand? That
> >> should be the ideal architecture IMHO.
> >>
> >
> > Two good reasons to allow git repositories as a source:
> >
> > 1) Many projects don't make tarball releases.
> >
>
> That does not mean bitbake cannot generate tarball out of the git
> repository. In fact, it is relatively simple. ;-)
It does, all you need to do is enable BB_GENERATE_MIRROR_TARBALLS
Versioned tarballs are already tracked by
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1511
> > 2) It's incredibly useful to be able to build from git snapshots for
> > development/testing purposes.
> >
>
> I was explicitly mentioning stable and official released variants.
>
> What you're asking for is the inability to use git repositories in SRC_URI,
> > which won't happen.
> >
>
> No, that is not what I am asking.
>
> Here you can find the feature request:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5035
>
> Cheers, L.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-08-21 11:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 11:40 Why is "bitbake core-image-minimal" building gtk docs? Laszlo Papp
2013-08-16 12:15 ` Jack Mitchell
2013-08-21 7:55 ` Laszlo Papp
2013-08-21 8:40 ` Jack Mitchell
2013-08-21 10:04 ` Burton, Ross
2013-08-21 10:16 ` Laszlo Papp
2013-08-21 10:21 ` Burton, Ross
2013-08-21 10:24 ` Laszlo Papp
2013-08-21 10:26 ` Burton, Ross
2013-08-21 10:31 ` Laszlo Papp
2013-08-21 11:04 ` Martin Jansa [this message]
2013-08-21 11:10 ` Laszlo Papp
2013-08-21 14:59 ` Richard Purdie
2013-08-21 15:01 ` Laszlo Papp
2013-08-29 16:19 ` Laszlo Papp
2013-08-29 17:15 ` Laszlo Papp
2013-08-30 13:42 ` Laszlo Papp
2013-08-29 15:01 ` Laszlo Papp
2013-08-29 15:10 ` Martin Jansa
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=20130821110401.GG522@jama \
--to=martin.jansa@gmail.com \
--cc=lpapp@kde.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 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.