[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#726533: RFS: 0install/2.3.3-2 [ITP] -- rename and split zeroinstall-injector package



On 2013-12-23 19:59, Vincent Bernat wrote:
  ❦ 23 décembre 2013 15:22 CET, Thomas Leonard <talex5@gmail.com> :

You are renaming the source package. Is it really necessary? This is
possible, but it is a bit painful to manage. With a new source package,
you need to issue a -1 version. This means to add an epoch to let your
transitional package take over the previous binary package.

Keeping the same source package name and just changing the binary
package names would be far easier.

OK, I've changed the source name back to how it was and uploaded the
new version here:

http://mentors.debian.net/package/zeroinstall-injector

Can it be approved now?

I didn't noticed that the non-core package does not contain any
file. You don't need to make a new package just for that. Demotes the
python-gtk2 dependency to a recommends (usually installed, but not
mandatory) or a suggests (usually not installed).

That's currently the case, but probably won't be for long. The next version (which is nearly ready) is written in OCaml rather than Python. At that point, I'll probably separate the GTK plugin from the main binary.

I could keep it as a single package (I don't really mind). Would it trigger any warnings to include a binary that depends on symbols that aren't required dependencies of the package?



Reply to: