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

Re: Looking for a sponsor for a new game 'curseofwar'



Thanks a lot, Bas.

> I can do that.  Let me know when you have fixed the above.
Done. 
1. I left the bin in  /usr/bin
2. Added cureofwar.menu (with a icon :) )
3. hardening-no-fortify-functions happens only when I build pkg on my PC. In PPA build all ok.

So, I fixed issues from Markus and Bas.
A new version (1.1.6-1) is avaible here : http://mentors.debian.net/package/curseofwar

Please, let me know if something else is wrong.

Best wishes,
Anton Balashov


2013/7/21 Bas Wijnen <wijnen@debian.org>
My mails to the list don't seem to arrive, so I'm sending it privately
(as well as attempting to the list, but I don't expect it to arrive
there).  Feel free to quote anything in public, in particular on the
games list. (reply-to set.)

On Sat, Jul 20, 2013 at 10:33:27PM +0400, Anton Balashov wrote:
> > - Please install your binary to /usr/games and not to /usr/bin
> In new Filesystem Hierarchy Standard 3.0 bin from games should be placed in
> /usr/bin.
> https://www.linux.com/learn/tutorials/476610-a-look-at-the-filesystem-hierarchy-standard-30
> https://bugs.linuxfoundation.org/show_bug.cgi?id=766
> It's strange to make a change for old standart. And even if do that, that's
> not good for game. Should I do a patch only for debian pkg?

We have discussed this before in the team; there wasn't really a
conclusion, but I think most people agreed that using /usr/games wasn't
really useful.  If /usr/games is dropped in the new FHS, I think we
should follow it.

> > You should add a desktop and menu file and icons to your package
> This game running in console only. Should I do a desktop and menu file in
> this case?

Yes; every application should show up in the menu.  In the case of
console applications, they should open a terminal and run there.

> And I can't win a lintian warning: hardening-no-fortify-functions
> I added next to debian/rules:
>
> *export DEB_BUILD_MAINT_OPTIONS = hardening=+all*
> *DPKG_EXPORT_BUILDFLAGS = 1*
> *include /usr/share/dpkg/buildflags.mk*
>
> And it didn't help me. Could you, please, hint me about that? :)

I didn't look at your package yet, but the usual reason is that the
flags are not passed to the build system (or are at least not used by
it).  Note that you don't need any of the above if you use debhelper
compatibility level 9 or above.  Check openmsx-catapult for a package
where I had to work around this problem as well; it has a custom build
system and I needed to add a debian patch to pass the flags in from
debian/rules.

> P.S.
> I'm looking for a sponsor for this game :)

I can do that.  Let me know when you have fixed the above.

By the way, do you want to maintain this as part of the games team?  In
that case you should request to be a member, and when you've got commit
access, add the packaging to our repository.

Thanks,
Bas


Reply to: