StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2964188
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-06-03T08:03:27.947
FavoriteCount
0
LastActivityDate
2010-06-03T08:12:18.713
LastEditDate
2010-06-03T08:12:18.713
LastEditorUserId
76138
OwnerUserId
76138
ParentId
2924801
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The key question here is: can your software X be distributed if you license X only under the MIT license (or some other rather relaxed Open Source license)? The answer to that question is: <ul> <li>no if the dependency of X on the GPL-licensed library Y is mandatory and cannot be avoided to build/use X.</li> <li>yes if the dependency of X on the GPL-licensed library is optional Y, and if it is disabled by default.</li> </ul> If the dependency on Y cannot be avoided, then releasing X under MIT would essentially prevent anybody (e.g. Linux distributions, or commercial vendors, or web-sites providing pre-built software) from distributing your software with the GPL-licensed library enabled in the build. So while you can decide to license your own software under the MIT license, by releasing it under this license you would create headaches for all your users. And my guess it that it is not what you are looking for. My recommendation is that you make up your mind and decide between either: <ul> <li>Release X under the GPL if this GPL-licenced library Y is essential to your software. (the simplest, do-the-right-thing option)</li> <li>Release X under dual GPL/MIT license if the GPL-licensed library Y is optional, and if you really need to have a version of software available under an MIT license, but want to allow distribution (by you or others) of X with Y support enabled. (only if it is really required)</li> <li>Release X under MIT if the GPL-licensed library Y is optional, but be aware that nobody will be able to distribute your software in any way with the Y support enabled. (creates potential headaches for users, for a really unclear benefit)</li> </ul> I hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLicensing software that uses GPL code with licenses other than GPL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USLaurent
UserOwnerUserId
1. USLaurent
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COMIT+GPL=GPL, so your third bullet point would be actually GPL for the aggregate.
 singulars
 PostPostId
 PO
 UserUserId
 USninjalj

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.