Re: Is this really the debian way ?
Hi,
On 08/02/14 20:13, Roelof Wobben wrote:
So they have to use some sort of "hack" to find the files of the second package.
If this is the way Debian wants the packages, how can I do the same with dh7.
Not too sure about this part and what the actual question is...
All the parts are of a debian directory made by the Linux mint developers.
and on the faq is stated that it is better to make a debian diretory instead of using upstream.
I'm not too sure which FAQ you are referring to, perhaps [0], but you
should understand it the right way: it doesn't mean that you should
throw away everything what upstream has done, because it would be a
complete duplication of work, which would be a shame (especially if
upstream has a good enough and well maintained debian/ directory), but to:
1. try to get upstream to remove debian/ from their upstream source .tar.gz
2. if that doesn't work, repackage upstream to remove debian/ from the
package, but use the debian/ directory as basis for your work (again, if
it's of good quality and actively maintained i.e. less effort than
re-creating the whole debian/ from scratch).
As Cinnamon is on Github, you could probably do some smart
clone/branching magic to limit your effort keeping your debian/ in sync
with upstream's, but I'm no specialist here (I just read here and there
that git can do this kind of magic :-)), and/or provide Cinnamon
directly your improvements of their debian/ directory which are not
Debian specific (it's generally possible to package software in a way
that it works under Ubuntu, Debian and all their derivatives, possibly
after a rebuild).
Hope this clarifies and helps,
Eric
Roelof
[0]
https://wiki.debian.org/DebianMentorsFaq#What.27s_wrong_with_upstream_shipping_a_debian.2F_directory.3F
--
I'm subscribed on debian-java, debian-mentors, pkg-java-maintainers and
pkg-vdr-dvb-devel.
No need to CC me on these lists.
Reply to: