Although I'm the "culprit" in the second case, I don't have in any way
a problem with such a statement. The problem I mainly see is that who
will judge the necessacity of the change?
If as part of enhancements, bug fixing, performance improvements,
etc., code changes are justified (or though of
Joey Hess wrote:
> A few packages in debian use .Z files - I don't know if they have good
> reason or not. It seems to me we should use .gz files except where technical
> reasons don't allow it (like back when X didn't support .gz'd fonts). Is it
> worth making policy on this issue?
Some programs
[EMAIL PROTECTED] (Ian Jackson) writes:
> Does the policy list think it would be a good idea to add a piece to
> the policy manual asking maintainers who inherit a package and
> uploaders of NMU's not to change the layout, structure or style of the
> source code unless it is really necessary ?
No
Ian Jackson writes:
> Does the policy list think it would be a good idea to add a piece to the
> policy manual asking maintainers who inherit a package [...] not to
> change the layout, structure or style of the source code unless it is
> really necessary ?
Certainly not. Why discriminate against
"Michael" == Michael Alan Dorman <[EMAIL PROTECTED]> writes:
> As to putting something in policy, I'm sceptical---what real effect
> will it have? The people need to be told are least likely to pay
> attention to it.
I agree. W.R.T. debiandoc-sgml, is there any evidence anywhere that
Ardo has do
[EMAIL PROTECTED] (Ian Jackson) writes:
> The first case was dpkg, whose build system has been replaced with a
> fragile Byzantine monstrosity which depends on libtool and automake
> and is the source of several bug reports. Also, a directory was
> renamed without rhyme or reason ! I intend (whe
[EMAIL PROTECTED] (Ian Jackson) writes:
> Does the policy list think it would be a good idea to add a piece to
> the policy manual asking maintainers who inherit a package and
> uploaders of NMU's not to change the layout, structure or style of the
> source code unless it is really necessary ?
I u
For the second time recently I've wanted to do a bit of work on a
package I wrote which others have been making releases of, and find
that substantial and unwarranted reorganisations have taken place
which make the job a lot harder.
The first case was dpkg, whose build system has been replaced wit
A couple of those packages are mine, and it was just laziness
or oversight. In these cases they are bugs.
John
--
John Lapeyre <[EMAIL PROTECTED]>
Tucson,AZ http://www.physics.arizona.edu/~lapeyre
9 matches
Mail list logo
