Ticket #6423 (closed defect: fixed)

Bug contains 1 commit(s) | SVN Diffs for #6423

 

Opened 5 months ago

Last modified 2 months ago

request removal of debian directory

Reported by: ejb@... Assigned to: michaelow
Priority: major Milestone: 4.1.1
Component: config_build Version: Current
Keywords: Cc:
Load: Xref:
Java Version: Operating System:
Project (C/J): all Weeks:
Review: srl

Description

As the debian maintainer of icu, I would like to request removal of the debian directory from ICU's sources. I actually made this request some time ago in a private email discussion with George Rhoten, but I'll do so again in the tracking system. I'll outline my reasoning.

When I build debian packages for icu, I specifically ignore the debian directory in the package. For one thing, it is not kept up to date. For another thing, every debian-based distribution may potentially have to modify it, and such modifications are, by their nature, not going to be suitable for inclusion "upstream". Since I have to modify debian/changelog and other files with every new release, the debian directory in the ICU sources will always be behind the actual version in the debian package. In fact, since the names of libraries and so forth change, the debian directory that is there in the ICU sources won't even work for an end user who wants to build the packages. Changing these is something that falls to the debian maintainer. It would be a waste of time on the part of the ICU maintainers to try to do this.

Rather than having incorrect debian directories, I think it would be better not to have any at all. The debian directory is part of the "debianization" of a package, and should rightly live in the debian archive and not in the upstream package. Even for my own open source packages, one of which is officially in debian, I keep the debian directory separate from the upstream sources. I control my debian directories in a separate subversion repository, and should I eventually turn over maintenance of the packages to someone else, I would turn those over as well. The history of the debian directories in the upstream sources doesn't reflect reality, though they have been synchronized from time to time.

The only reason I could think of to have a debian director in the ICU sources would be if that directory actually made it possible for someone to download ICU and build their own debian packages. This would require that someone one the ICU development team tested the debian directories to make sure the packaging is correct. Additionally, since the ICU packages in debian have been in good shape and staying as current as allowable by debian's own release schedule, there is less reason for anyone to need to do this. I communicate any bugs posted to the debian packages with the ICU developers, and I also monitor the health of ICU in Ubuntu to make sure my ICU packages will work for both distributions.

Should I eventually become less diligent in my maintainer duties (unlikely) or should I eventually hand this off to someone else who does a worse job in keeping things up to date, then maybe it would make sense to consider inclusion of debian directories in the ICU sources once again.

In any case, this is just a request. It doesn't really matter that much to me since I systematically ignore the debian directories in the upstream sources. I just think it's misleading to people who download the packages to find debian directories that are out of date and don't work.

Thanks for your consideration.

Attachments

Change History

07/05/08 09:28:08 changed by ejb@...

Alternatively, we could decide to try to keep the debian directories in sync, but I would consider this "second best". If we want to do this, we should establish some mechanism. I always test draft releases but do not stay involved in the ICU development in any other way. I'm still not sure how we get around the fact that the debian files will necessarily always lag behind the real releases.

In the interest of full disclosure, I should say that George Rhoten was not in favor of removing them. Here are his comments from a private email dated 2006-08-15:

The previous maintainer of the ICU Debian packages kept both in sync with each other. Unless you plan on contributing updates, the files are going to stay where they are. You can send me the updates, and I can commit them for you.

At that time, I submitted the current debian directory along with a release form, and that is the last time they have been updated. The current files are for the 3.6 release.

(follow-up: ↓ 3 ) 07/08/08 01:47:03 changed by srl

  • xref changed.
  • priority changed from minor to assess.
  • milestone changed from UNSCH to 4.2.
  • owner changed from somebody to srl.
  • weeks changed.
  • revw changed.

As another historical note, the previous maintainer (who was, maybe is, a debian maintainer) did keep them updated. Downstream packagers are presumably the intended users of this directory. Do you know that no-one else uses the current directory? Since it is for 3.6, it is doubtful. I would probably think that removal and better communication with you (and all other downstream packagers) would be better.

(in reply to: ↑ 2 ) 07/08/08 10:06:46 changed by ejb@...

Replying to srl:

I know that when I arranged to have the debian directory updated to 3.6, it hadn't been updated prior to that for some time, so it's been a few years since anyone's kept it consistently up to date.

As for whether anyone else uses it, downstream packagers who are basing their distribution on debian would be better served to use the package as it appears in the debian archive with that debian directory and any patches. This is what Ubunutu does. Also worth noting is the fact that Debian is soon to migrate to a new source package format which will specifically ignore any upstream debian directories.

If, in spite of my recommendation to the contrary, you decide to keep the debian directory, I would be willing to work with you to keep it synchronized, but I still wouldn't think it's the right thing to do. :-)

07/21/08 09:37:29 changed by hchapman

  • priority changed from assess to major.
  • milestone changed from 4.2 to 4.1.1.

08/12/08 10:32:18 changed by hchapman

  • owner changed from srl to michaelow.

08/12/08 13:45:23 changed by michaelow

  • status changed from new to assigned.
  • revw set to srl.

The conclusion that I arrive at from looking at the previous discussions is that the removal of the debian directory is the preferred method of choice and that little consequences will come about because of it. So, I will go ahead and remove the debian directory from ICU4C. If, in the future, there arises a great need for the debian directory, we will consider resurrecting it once again.

09/17/08 16:09:24 changed by srl

  • status changed from assigned to closed.
  • resolution set to fixed.

Add/Change #6423 (request removal of debian directory)




Anti spam check: