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

Re: RFS: dwm





2011/8/31 Etienne Millon <etienne.millon@gmail.com>
* Jeremy Allard <elvis4526@gmail.com> [110831 07:32]:
> PS: I'm not really sure if it is te correct way to this. Please, correct me
> if i'm wrong. I know that dwm is already present in main, but its oudated
> and I have no news from the maintainer that i contacted by email a week ago.
>
> I would be thankfull if you could give me any advice on my package so i can
> make it better.
> Kind regards,

Hello,

Dwm is indeed part of the archive. Contacting the maintainer was a
good idea (a wishlist bug could have been enough, too), but one week
is a very short amount of time. What you are trying to do (orphaning
the package #639657) could be considered "an aggressive takeover" :-)

Another thing is that your source package does reuse the current one
at all (lintian complains about left dh_make templates). To hack on
packages, it's a better idea to start from the existing (that you can
obtain with apt-get source) and maybe to use a VCS helper such as
git-buildpackage ; that's what the maintainer is doing and you can see
his work on http://git.webconverger.org/?p=dwm .

If you want to upgrade dwm, the best thing to do is probably to wait a
little more for an answer from the maintainer. In the meantime, you
can prepare a new version on top of his work, and submit that to him.
If you don't have more news, then you can consider looking for a
sponsor for a NMU.

--
Etienne Millon


--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 20110831055826.GA3362@john.ssi.corp" target="_blank">http://lists.debian.org/[🔎] 20110831055826.GA3362@john.ssi.corp

Ok, thanks very much for the answer, I should have wait more time before doing all the steps. Thanks for the other advice, I will work with the package that he already made next time. And just for the curiosity, what you mean by left dh_make template? If the package doesn't need for exemple a post-install script, should-I delete it or (that's what I tought) I should keep it there but with nothing important in? I read all the maintainer guide, it's just that I want to do the best package. :-)
And by the way, I'm used  to use slackbuilds to make packages for Slackware, dh_make and dpkg-buildpackage are pretty awesome compare to those. :)


Reply to: