Re: About new fields in debian/control for bug reporting.
> - what happens if the package is listed in more then one origin-*
Well, an installed package can only have one origin, so I think you
may be misunderstanding my scheme. Here's an example:
Run "origin foo" and you'll get a control record which says bugs
should go to bugs.debian.org. "origin bar" says bugs go to wherever
you send bugs for Helix packages. "origin gak" returns something that
says send bug reports to email@example.com (the maintainer).
/etc/origin/Debian, /etc/origin/Helix, and /etc/origin/Maintainer
(from origin-debian, origin-helix, and origin-base respectively) don't
contain any information about particular packages. They just have
information about where bugs should go *for packages with that Origin
field*. Right now I have this (note the parts that get substituted):
> - if I wanted to package, say my website (something which isn't of
> general interest to the Debian project), would I also have to package
> a separate origin-* package so that bug reports (eg speling mistakes)
> come back to me? This would seem to me to be a slight overkill...
Well, how would someone who'd installed your packages know where to
send bug reports? The two templates above are, I think, the two main
cases: to a special bug tracking system, or back to the maintainer.
So I guess my answer is "Yes, but so what? Origin-yourstuff consists
of just one file, with just a few lines it!"
> Personally, I think it might be better if each package was responsible
> for its own bug tracking system.
I like the level of indirection the Origin field gives us. I'm
assuming that all packages from a particular origin will want to have
bugs submitted in the same way. So far, this seems to be the case.
My code is rooted in this assumption, so please correct me if I'm
PS. I see /etc/origin/* used for other origin-specific things. Where
to upload incoming packages, for example (not being a maintainer, yet,
I'm not really sure how that works).