Re: Your packaging of sumaclust today
Hi Pierre,
On Thu, Apr 02, 2020 at 10:15:23AM +0200, Pierre Gruet wrote:
> Please believe I did not intend to hide things, but only to reduce
> noise. Next time I shall use the mailing list.
I perfectly believe you. I just wanted to explain what might be
considered rude from my side. This list is fine for this kind of
general discussion. If it becomes really technicall, the maintainers
list (see "Maintainer:" field in d/control) is the right place but
we do not make a strict difference.
> > Actually that bug was pretty easy by setting a simple -I option in
> > Makefile. I admit I wonder why that has build before at all. Seems
> > upstream has found a different fix since my patch did not created any
> > conflict when importing and building the new upstream version.
> I do not understand how that built before. We discussed this with
> upstream yesterday.
Fine. As I said, feel free to revert parts of my patch. BTW, I
injected additional CFLAGS in the patch as well (which is strictly
speaking dirty since not documented). So Debian builds with -g flag to
create a debug package automatically and strips the executable later.
That's also included into my patch.
> > 1. Would create a salsa.d.o login
> > 2. Join the Debian Med team
> > 3. Read Debian Med team policy[2] in case you might not be
> > comfortable with usual workflows in team similar to
> > 4. Add yourself as Uploader to all packages you would
> > volunteer to package
> > 5. Review my work! (Well, I have some routine but it might
> > be wrong. May be there is a better fix in sumaclust than
> > tweaking the Makefile in a quilt patch.)
> > 6. Review sumalibs packaging - we could definitely use also
> > a dynamic library since we should avoid code duplication
> > in sumaclust and sumatra
> > 7. Enjoy beeing member of the Debian Med team
> >
> > Thanks again for your attempt to help
> Thanks for that detailed proposal. Yes, I would like to join the team
> and asked for it in Salsa.
:-)
> If I may add something: having read the policy some days ago, I feel it
> lacks a kind of ``general habits'' section, like what you explained
> above: is it casual/rude to begin working on a package that already has
> uploaders who uploaded recently without asking them, for instance? The
> general Debian documentation would strongly advise against doing so, but
> what about team work?
Ahhhh, really nice hint. Yes, we should mention this explicitly!
> You answered this concerning Debian Med Project.
> Of course this is not a critics to anyone, just a newcomer's feeling.
I'm personally even open for critics. That's fine. And here you have a
really valid point. It would be soooo cool if I would simply put this
in policy and would get rid of all my Uploaders duties in the next
month. ;-)
> > [1] https://salsa.debian.org/science-team/routine-update
> > [2] https://med-team.pages.debian.net/policy/
> >
> Have a great day,
Same to you
Andreas.
--
http://fam-tille.de
Reply to: