Mailinglist Archive: opensuse-packaging (186 mails)

< Previous Next >
Re: [opensuse-packaging] Question for packaging python apps
  • From: Jan Matejek <jan.matejek@xxxxxxxxxx>
  • Date: Thu, 05 Feb 2009 19:17:58 +0100
  • Message-id: <498B2D56.5020208@xxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Vidner napsal(a):
On Thu, Feb 05, 2009 at 12:24:26PM +0100, Vincent Untz wrote:
Hi,

I have a python app that installs all its .py files in
${_datadir}/%{name}, and upstream thinks it's right. I thought it made
sense to put the files in %{py_sitedir}/%{name}, so I originally had a
patch to do this, but if upstream doesn't want it, I'm not really keen
on keeping it.

Is there any policy for this?

If those files are private to the app, as opposed to usable by
others as a library, then ${_datadir}/%{name} is a reasonable
private storage and I see no reason to diverge from upstream.

Actually it's a little more difficult than that - what you (and
upstream) are doing is directly against FHS, which states that program
files aren't supposed to go anywhere near ${_datadir}.

General recommendation is to put everything in %{py_sitedir}.
But it's not a policy (yet), because this approach also has some
drawbacks... And python upstream doesn't have a strong opinion on this
either, that's the worst part.

so, simple answer is, keep the files where upstream wants them, until
somebody comes up with a better way. (and when that somebody does, i'll
keep you posted)

regards
m.

- --
(if you have any comments, please CC me in the reply, otherwise my
replies will break threads. that is a bug in my way of using the
mailinglist, which is not yet fixed)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkmLLVYACgkQjBrWA+AvBr951gCfdN9uI1h7hiw7NCLDB0aZnwZA
TqUAnR0+OA+zPObVa4uxt9Tz6rbxq0jK
=22z4
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups