Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Uncommon source deployment policy of live555
Date: Fri, 25 Nov 2011 12:05:46 +0100	[thread overview]
Message-ID: <4ECF768A.4060108@dresearch-fe.de> (raw)

The LIVE555 project has a really uncommon source deployment policy. :(

They publish *only* the latest tarball of their code [1]. And they don't make the code available under a source code repository [2].

I've asked to change this policy but they are not willing to do that [3].

How can we handle this?
Does OE provides a "mirror" server to provide the versions we're referencing? How can we upload versions there?
Which changes to the recipes are necessary to use it?

Regards,
Steffen

[1] <http://www.live555.com/liveMedia/faq.html#old-versions>
[2] <http://www.live555.com/liveMedia/faq.html#no-source-code-repository>
[3] see thread <http://lists.live555.com/pipermail/live-devel/2011-November/014127.html>

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058



             reply	other threads:[~2011-11-25 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 11:05 Steffen Sledz [this message]
2011-11-25 11:21 ` Uncommon source deployment policy of live555 Koen Kooi
2011-11-25 11:29   ` Steffen Sledz
2011-11-26  5:49     ` Khem Raj
2011-12-06  7:07       ` Steffen Sledz
2011-12-07 13:50         ` Steffen Sledz
2011-12-07 16:20           ` Khem Raj

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=4ECF768A.4060108@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --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