Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.java > #8363

Re: Splitting the Java policy from java-common

From tony <tmancill@debian.org>
Newsgroups linux.debian.maint.java
Subject Re: Splitting the Java policy from java-common
Date 2015-09-22 17:20 +0200
Message-ID <qbxwm-DB-31@gated-at.bofh.it> (permalink)
References <qbtCp-3y2-1@gated-at.bofh.it> <qbx3j-8hS-1@gated-at.bofh.it> <qbxd0-8t1-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Tue, Sep 22, 2015 at 04:59:23PM +0200, Emmanuel Bourg wrote:
> Le 22/09/2015 16:44, Markus Koschany a écrit :
> 
> > I agree with Thorsten that this would imply a packaging overhead for
> > only a little gain. Although I think that splitting the documentation
> > would be cleaner, it is probably not worth the effort for a few KB. No
> > strong preferences from my side though.
> 
> Thank you for the feedback. I'm suggesting this change mainly for a
> better separation of concerns, the space saved is obviously
> insignificant. For example a separated policy makes it possible to
> upload an updated default-jre package in experimental and then publish
> policy changes in unstable without waiting for java-common to transition
> to unstable.

I also believe the benefits outweight the cost of having another package
in the archive.  We may want to iterate over policy frequently, and do
so without triggering upgrades for every installed copy of java-common.
In that case, a separate package may take a bit more disk on the
mirrors, but it could also result in less overall network bandwidth.

It would also be nice if the policy package was named something
obvious, like java-policy. :)

Cheers,
tony

Back to linux.debian.maint.java | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Splitting the Java policy from java-common Emmanuel Bourg <ebourg@apache.org> - 2015-09-22 13:10 +0200
  Re: Splitting the Java policy from java-common Jan Henke <Jan.Henke@taujhe.de> - 2015-09-22 14:00 +0200
  Re: Splitting the Java policy from java-common Thorsten Glaser <t.glaser@tarent.de> - 2015-09-22 14:00 +0200
    Re: Splitting the Java policy from java-common Emmanuel Bourg <ebourg@apache.org> - 2015-09-22 19:50 +0200
  Re: Splitting the Java policy from java-common Markus Koschany <apo@gambaru.de> - 2015-09-22 16:50 +0200
    Re: Splitting the Java policy from java-common Emmanuel Bourg <ebourg@apache.org> - 2015-09-22 17:00 +0200
      Re: Splitting the Java policy from java-common tony <tmancill@debian.org> - 2015-09-22 17:20 +0200
        Re: Splitting the Java policy from java-common Emmanuel Bourg <ebourg@apache.org> - 2015-09-22 17:40 +0200
        Re: Splitting the Java policy from java-common Thorsten Glaser <t.glaser@tarent.de> - 2015-09-22 17:40 +0200
          Re: Splitting the Java policy from java-common Emmanuel Bourg <ebourg@apache.org> - 2015-09-22 18:00 +0200
            Re: Splitting the Java policy from java-common Thorsten Glaser <t.glaser@tarent.de> - 2015-09-22 18:10 +0200
            Re: Splitting the Java policy from java-common Markus Koschany <apo@gambaru.de> - 2015-09-23 00:00 +0200
  Re: Splitting the Java policy from java-common Emmanuel Bourg <ebourg@apache.org> - 2015-09-23 10:00 +0200
    Re: Splitting the Java policy from java-common Markus Koschany <apo@gambaru.de> - 2015-09-23 11:20 +0200
      Re: Splitting the Java policy from java-common Miguel Landaeta <nomadium@debian.org> - 2015-09-23 15:40 +0200

csiph-web