Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository

Theoretically, yes, it does open possibility for bad things to happen.
In practice, however, this worked for us for last three releases. If
there was an easy way to consume current simrel dependencies from the
build, I'd certainly do it, but I am not willing to spend any time on
this when building against previous simrel repo works good enough.

--
Regards,
Igor

On 2013-08-21 10:08 AM, Doug Schaefer wrote:
I'm with David on this one. The simrel repo is supposed to be the
aggregation of all the project builds. If you are building against an old
simrel repo, chances are you aren't building against the bits that will
appear with your bits in this round's simrel repo. Doesn't that open up
the potential for bad things?

Doug.

On 13-08-21 7:29 AM, "Igor Fedorenko" <ifedorenko@xxxxxxxxxxxx> wrote:

I did the same, too. I simply don't have the time needed to maintain
list of project-level repositories and will build against kepler until I
can switch to luna simrel repo.

--
Regards,
Igor

On 2013-08-21 4:05 AM, Marcel Bruch wrote:
Maybe it would help if project could publish a (stable) URL of their
latest Luna artifacts on a common wiki page? I had trouble to find all
dependencies and features to set up our target platform accordingly two
weeks ago. So decided to build the software against Kepler instead.

Best,
Marcel

On Aug 21, 2013, at 9:57 AM, David M Williams <david_williams@xxxxxxxxxx
<mailto:david_williams@xxxxxxxxxx>> wrote:

Yes, has been discussed before, and I said "bad idea", because anyone
building for the Luna repository, should not be building against the
Luna repository.




From: Eike Stepper <stepper@xxxxxxxxxx <mailto:stepper@xxxxxxxxxx>>
To: cross-project-issues-dev@xxxxxxxxxxx
<mailto:cross-project-issues-dev@xxxxxxxxxxx>,
Date: 08/21/2013 03:49 AM
Subject: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
<mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx>

------------------------------------------------------------------------



Hi,

I noticed that an empty Luna repository had been created some time
after the release of Kepler. An empty repository is
not really useful as a source for build dependencies and I wondered if
it would make sense in the future to seed the new
repository with the old content. Would it? Has it been discussed
already?

Cheers
/Eike

----
http://www.esc-net.de <http://www.esc-net.de/>
http://thegordian.blogspot.com <http://thegordian.blogspot.com/>
http://twitter.com/eikestepper


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
<mailto:cross-project-issues-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
<mailto:cross-project-issues-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top