From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alexander@mezon.ru
Cc: poky@yoctoproject.org
Subject: Re: building rpm distro
Date: Thu, 04 Oct 2012 11:40:51 +0100 [thread overview]
Message-ID: <1349347251.18301.80.camel@ted> (raw)
In-Reply-To: <1349346798.6218.8.camel@localhost>
On Thu, 2012-10-04 at 14:33 +0400, Alexander Khryukin wrote:
> Also in meta/lib/oe/distro_check.py
> i see function
>
>
> def get_latest_released_mandriva_source_package_list():
> "Returns list of all the name os packages in the latest mandriva
> distro"
> latest =
> find_latest_numeric_release("http://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/devel/")
> package_names =
> get_source_package_list_from_url("http://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/devel/%s/SRPMS/main/release/" % latest, "main")
> # package_names +=
> get_source_package_list_from_url("http://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/%s/SRPMS/contrib/release/" % latest, "contrib")
> package_names +=
> get_source_package_list_from_url("http://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/devel/%s/SRPMS/main/updates/" % latest, "updates")
>
> package_list=clean_package_list(package_names)
> return latest, package_list
>
>
> It will downloads SRPMs from repo and build them, right?
No, this is part of the license checking code where we check which other
distributions contain a given piece of software for various reasons.
We do not download and build SRPMs directly.
Cheers,
Richard
next prev parent reply other threads:[~2012-10-04 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 9:35 building rpm distro Alexander Khryukin
2012-10-04 10:24 ` Richard Purdie
2012-10-04 10:26 ` Alexander Khryukin
2012-10-04 10:33 ` Alexander Khryukin
2012-10-04 10:40 ` Richard Purdie [this message]
2012-10-04 10:39 ` 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=1349347251.18301.80.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander@mezon.ru \
--cc=poky@yoctoproject.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.