Mailinglist Archive: opensuse-gnome (124 mails)

[Magnus Boman <captain.magnus@xxxxxxxxx>]

Luis,

On Fri, 2009-01-30 at 01:07 +0000, Luis Medinas wrote:
> On Fri, 2009-01-30 at 12:02 +1100, Magnus Boman wrote:
> > Hello,
> >
> > Currently, when doing package updates, we have some (strange) policy
> > that we have to put in what changes upstream made (ie, bugfixes, new
> > features etc).
> >
> > All this information is already available in the NEWS/ChangeLog file for
> > most packages.
> >
> > Since this doesn't seem to be an openSUSE policy [1] I wonder why we
> > enforce this for GNOME components?
> >
> > Enforcing updates of the changelog makes it possible to check details of
> > upstream changes with;
> >
> > # rpm -q --changelog nautilus
> >
> > By not enforcing these changes, one can do;
> >
> > # cat /usr/share/doc/packages/nautilus/NEWS
> >
> > I see little (if any) value in doing this, but it adds a lot of time
> > when doing a package update, so I would like to change the policy to
> > simple contain specific updates that the packager made (add/remove patch
> > etc)
> >
> > Opinions?
> My opinion is that we should stick with the current policy, since is the
> team maintaining all packages(everyone can bump a pkg) it's useful to
> know what changed from a release to another, specially what dirty hacks,
> workarounds and dependencies were remove along with new features
> introduced that might not be enabled. Also it keeps easier to keep
> tracking bugs on upstream -> bnc.

I didn't mean that packagers shouldn't have to explain their "dirty
hacks" etc in the changelog. I'm strictly talking about what's already
available in NEWS/Changelog files, which is redundant information that
is already available and a cause of wasting time, especially since I
don't believe that a whole lot of people ever use it.

Cheers,
Magnus


-- 
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx