On 06/24/2013 11:59 AM, Aleksandar Kurtakov wrote:
I believe Debian relaxes the OSGi-generated dependencies on system
libraries. Fedora should do the same thing in its Eclipse packaging.
Just to clarify a bit - this is not a limitation of OSGi. It's the Eclipse
implementation being faulty of
Le Lun 24 juin 2013 11:59, Aleksandar Kurtakov a écrit :
> This shows another problem though: expressing version range in a spec file
> e.g there is no easy way to say I want a package that provides osgi(smth)
> [1.0.0, 1.5.0). If you try to express it with RPM requires as two
> statements:
> Req
Krzysztof,
unrelated to this thread, but I've noticed the "Face" header in your
email, which exceeds the maximum size of such headers. As such, it breaks
the hard limits of some servers as well as clients, such as Claws Mail.
http://quimby.gnus.org/circus/face/
--
Fedora release 19 (Schrödinge
- Original Message -
> From: "Florian Weimer"
> To: devel@lists.fedoraproject.org
> Sent: Friday, June 21, 2013 3:00:36 PM
> Subject: Re: A need for build triggers & automatic rebuilds
>
> On 06/21/2013 08:28 AM, Krzysztof Daniel wrote:
>
&g
On 06/21/2013 08:28 AM, Krzysztof Daniel wrote:
OSGI records that there is a file
org.eclipse.jetty.http_9.0.3.v20130506.jar that holds a plugin with
version 9.0.3.v20130506. That version goes at the build time in a couple
of places (including metabundle).
Such exact dependencies are fundament
On Wed, 2013-06-19 at 12:23 +0200, Nicolas Mailhot wrote:
> Le Mer 19 juin 2013 10:07, Krzysztof Daniel a écrit :
> > Hello everyone,
>
> > I'd like to be able to define a build trigger for Eclipse, so when a
> > "vital" dependency changes, Eclipse is rebuild, BR/R are updated, and a
> > bodhi upd
On Wed, 2013-06-19 at 10:00 -0600, Eric Smith wrote:
> On Wed, Jun 19, 2013 at 4:23 AM, Nicolas Mailhot
> wrote:
> > You don't need a special trigger. You need your requirements to match the
> > constraints declared at the rpm level, then incompatibilities will be
> > caught at this level by norma
On Wed, Jun 19, 2013 at 4:23 AM, Nicolas Mailhot
wrote:
> You don't need a special trigger. You need your requirements to match the
> constraints declared at the rpm level, then incompatibilities will be
> caught at this level by normal distro tooling.
How does that work? A pointer to the docs i
Le Mer 19 juin 2013 10:07, Krzysztof Daniel a écrit :
> Hello everyone,
> I'd like to be able to define a build trigger for Eclipse, so when a
> "vital" dependency changes, Eclipse is rebuild, BR/R are updated, and a
> bodhi update is performed. And I get a notification :-).
>
> Is there a way to
On 06/19/2013 10:07 AM, Krzysztof Daniel wrote:
I'm responsible for packaging Eclipse, which is *very* vulnerable to the
change of certain subset (10-15 or so) of its dependencies. The point is
that those dependencies, when rebuilt, frequently change their version,
and Eclipse is unable to start
Hello everyone,
I'm responsible for packaging Eclipse, which is *very* vulnerable to the
change of certain subset (10-15 or so) of its dependencies. The point is
that those dependencies, when rebuilt, frequently change their version,
and Eclipse is unable to start in most cases.
I'd like to be ab
11 matches
Mail list logo
