<div class="gmail_quote">On Tue, Dec 1, 2009 at 09:39, Alan Hicks <span dir="ltr"><<a href="mailto:alan@lizella.net">alan@lizella.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Apologies Grissiom, if you're on our mailing list and receive this<br>
message twice.<br>
<div class="im"><br></div></blockquote><div><br></div><div>Actually I'm on the mailing list but doesn't receive it twice. Hmm, maybe GMail can remove duplicated mail automatically?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
On Tue, 1 Dec 2009 09:27:27 +0800<br>
Grissiom <<a href="mailto:chaos.proton@gmail.com">chaos.proton@gmail.com</a>> wrote:<br>
<br>
> I'm writing a SlackBuild for Mendeley Desktop<br>
> ( <a href="http://www.mendeley.com" target="_blank">http://www.mendeley.com</a> ), which is a research paper management<br>
> tool. But I found two problems there.<br>
><br>
> 1, It's a proprietary software, although you can use for free(free<br>
> beer but not free speech) as long as you agree with it's 'terms and<br>
> conditions'. Is it enough that I notice it in the README and let<br>
> users be aware of it?<br>
<br>
</div>That should be fine. Put it at the top of the README as it's own<br>
sentence/paragraph all by itself so it stands out and I don't think<br>
anyone will mind. The software may well be proprietary, but we're only<br>
distributing build scripts, not the software or the source code, so<br>
we're not really covered by whatever license that software is under.<br>
<div class="im"><br></div></blockquote><div><br></div><div>Yup, thanks for explanations. Then I know what should I do now.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
> 2, It seems that the package have to make a /share directory. As it<br>
> lays in the very root, I doubt whether it is something that a<br>
> user-space package should do. I know I can link /share to /usr/share<br>
> and pull things there. But we will have a /share eventually.<br>
<br>
</div>Now that's ugly as sin in Sunday School. Are you absolutely certain<br>
that things have to be placed in /share? I'm thinking that this<br>
software may most properly be placed (nearly) completely under /opt<br>
such as is done with <a href="http://openoffice.org" target="_blank">openoffice.org</a>. If it absolutely has to go<br>
under /share, I guess that's something the admins will have to<br>
consider. To the best of my knowledge, no software build script has<br>
ever required the creation of a new top-level directory.<br>
<font color="#888888"><br></font></blockquote><div><br></div><div></div></div><div>Oops, sorry for disturbing. It's my fault. Everything would work fine when placed under /usr(including the share folder). So there is no problem now ;-) Thanks for your explanation.</div>
<br>-- <br>Cheers,<br>Grissiom<br>