> However, it must not be
> the case that my package installs database_gap without asking the user.

That's also what I understood. You can return an error if the other
thing is not installed, but not add the dependency yourself.

Alternatively, and because your package can never become standard
(because of this dependency), you can simplify the user's workflow a
bit and add an interactive license agreement to you spkg-install file:
it would tell the user what is about to happen, have him "accept the
license", and then install the dependency.

I think that it can legally work, but I would wait for a confirmation
of somebody who knows such matters better than I. Similarly for a
non-legal advice about interactive spkg-install.

Have fuuuuuuuuuun,

Nathann

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to