Bug#783308: RFS: mediagoblin/0.7.1+dfsg1-1 [ITP]
On Fri, May 15, 2015 at 9:27 PM, Simon Fondrie-Teitler wrote:
> I looked into packaging them separately, but couldn't find good
> documentation on how to package css or javascript files. A few Debian
> developers I talked recommended not packaging them on their own.
For JavaScript, check out the many libjs-* examples in the archive.
For CSS, it would just be a matter of installing the files in
/usr/share/ somewhere and having mediagoblin refer to them. Embedded
code copies are against policy. The world of web software however
often plays fast and loose with APIs, often very specific versions are
required. I guess that is why people are recommending embedded code
copies. Personally I recommend packaging those versions separately, as
we do for GCC or Python itself.
https://wiki.debian.org/EmbeddedCodeCopies
> I've talked to upstream about the files, and some will be removed in the
> new release, like the binary translation files. Others need to be
> there to make it easy for people installing via pip or a git checkout,
> like the javascript.
Thanks. Hmm, ok.
> That's a good idea, although the version in README.Debian is closer to
> an example of one possible setup, rather than a suggested way of running
> it. I'm still thinking about the best way of doing this. I'm assuming
> it's not a blocking issue for package upload?
Not a blocking issue.
> I tried doing this, but the script won't even succeed showing help
> output when run without mediagoblin/tools/common.py somewhere on the
> python path. I'm not sure if it's a good idea to modify the python path
> during build.
It would be fine to set/modify PYTHONPATH for the manual page build
command, probably not other stuff though.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Reply to: