What is the difference between 'contrib' and 'non-free' packages repositories? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionI can't use or find the google debian unstable/sid repositoryTrouble migrating from Yum to apt-getHow to find Debian packages that would free up the most spaceuninitialized constant XML::SaxParser / Error retrieving bug reports from the serverDifference between Linux Mint Debian Edition (LMDE) and Debian with CinnamonBuilding and installing packages from unstableDebian stretch package system breaks when non-free addedHow to pass extra flags to the configure utility to a package from the Debian repositories?Maintaining a local Arch repositoryHow to delete all non-free or contrib packages?
How to bypass password on Windows XP account?
How to deal with a team lead who never gives me credit?
Why don't the Weasley twins use magic outside of school if the Trace can only find the location of spells cast?
Right-skewed distribution with mean equals to mode?
Is a manifold-with-boundary with given interior and non-empty boundary essentially unique?
Why are there no cargo aircraft with "flying wing" design?
What are the pros and cons of Aerospike nosecones?
How can I make names more distinctive without making them longer?
Is the address of a local variable a constexpr?
"Seemed to had" is it correct?
Can inflation occur in a positive-sum game currency system such as the Stack Exchange reputation system?
Does accepting a pardon have any bearing on trying that person for the same crime in a sovereign jurisdiction?
Is 1 ppb equal to 1 μg/kg?
Is it true that "carbohydrates are of no use for the basal metabolic need"?
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
Why aren't air breathing engines used as small first stages
Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?
Is there a "higher Segal conjecture"?
Were Kohanim forbidden from serving in King David's army?
What would be the ideal power source for a cybernetic eye?
The logistics of corpse disposal
What happens to sewage if there is no river near by?
Is there a concise way to say "all of the X, one of each"?
What's the purpose of writing one's academic bio in 3rd person?
What is the difference between 'contrib' and 'non-free' packages repositories?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionI can't use or find the google debian unstable/sid repositoryTrouble migrating from Yum to apt-getHow to find Debian packages that would free up the most spaceuninitialized constant XML::SaxParser / Error retrieving bug reports from the serverDifference between Linux Mint Debian Edition (LMDE) and Debian with CinnamonBuilding and installing packages from unstableDebian stretch package system breaks when non-free addedHow to pass extra flags to the configure utility to a package from the Debian repositories?Maintaining a local Arch repositoryHow to delete all non-free or contrib packages?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Although I like Debian for various reasons, it is not always easy to find some documentation on specific aspects of this distribution and its policies.
My question is: what is the difference between contrib
and non-free
packages repositories?
From the little explanations I could find, if I am not mistaken:
non-free
is for packages whose licences are not freecontrib
for dependencies ofnon-free
packages (which make them not part of Debian)
But it seems odd to me to have two repositories for, so to speak, the same purpose, which is making available non free software inside Debian.
I would like to know if I am missing something here.
debian repository debian-policy
add a comment |
Although I like Debian for various reasons, it is not always easy to find some documentation on specific aspects of this distribution and its policies.
My question is: what is the difference between contrib
and non-free
packages repositories?
From the little explanations I could find, if I am not mistaken:
non-free
is for packages whose licences are not freecontrib
for dependencies ofnon-free
packages (which make them not part of Debian)
But it seems odd to me to have two repositories for, so to speak, the same purpose, which is making available non free software inside Debian.
I would like to know if I am missing something here.
debian repository debian-policy
add a comment |
Although I like Debian for various reasons, it is not always easy to find some documentation on specific aspects of this distribution and its policies.
My question is: what is the difference between contrib
and non-free
packages repositories?
From the little explanations I could find, if I am not mistaken:
non-free
is for packages whose licences are not freecontrib
for dependencies ofnon-free
packages (which make them not part of Debian)
But it seems odd to me to have two repositories for, so to speak, the same purpose, which is making available non free software inside Debian.
I would like to know if I am missing something here.
debian repository debian-policy
Although I like Debian for various reasons, it is not always easy to find some documentation on specific aspects of this distribution and its policies.
My question is: what is the difference between contrib
and non-free
packages repositories?
From the little explanations I could find, if I am not mistaken:
non-free
is for packages whose licences are not freecontrib
for dependencies ofnon-free
packages (which make them not part of Debian)
But it seems odd to me to have two repositories for, so to speak, the same purpose, which is making available non free software inside Debian.
I would like to know if I am missing something here.
debian repository debian-policy
debian repository debian-policy
asked Apr 1 at 16:53
ParadoxParadox
517418
517418
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
non-free packages are packages not complying to the Debian Free Software Guidelines definition. E.g.:
nvidia-driver
which provides a proprietary driver.
contrib packages are packages that do comply with the DFSG, but depend on non-free packages, or which depend on some non-free software downloaded (by the package or having to be downloaded manually) to work properly. So they don't end up in main
. E.g.:
bumblebee-nvidia
which while DFSG compliant, isn't really useful without the non-free package nvidia-driver
, so it's put in the contrib
section, or
vice
which requires to download (while respecting copyrights and laws) ROMs to work properly.
If somebody doesn't want to or can't use non-free software, that person most probably doesn't need or won't be able to use software depending on it, so it's more useful to put them separately in a contrib section. That person won't even have to download the contrib section.
UPDATE: the software in contrib, and its sources are still available for free use. Interesting parts could be reused in an other project, or the non-free (or non available) parts it depends upon could be replaced (e.g.: replace graphics, music etc. assets for a game engine in contrib). Having it separate from non-free helps to know which parts can be reused.
trivia: the Open Source Definition was initially created by removing any mention of Debian in DFSG.
2
I don't really understand the benefit to either Debian or its users of seperatingnon-free
andcontrib
. What is the actual advantage gained? As an end-user who doesn't care if a program contains non-free code, bothnon-free
andcontrib
are fine by me. As an end-user who does care, both are off-limits for me. What is the actual advantage?
– MechMK1
Apr 2 at 8:40
1
Like MechMK1, I am puzzled by this, and, even if I should have maybe have it written clearer in my question, that is also an aspect I would like to an answer to.
– Paradox
Apr 2 at 9:12
1
You can reuse and modify code from contrib to adapt it to an other project, because the source is available as any source from "main". You probably can't do this when it's from non-free, either the source licence doesn't let you do enough, or there is no source at all. If the end user is a "normal" end user who doesn't attempt to do anything beside what is distributed, I can imagine contrib and non-free would look the same
– A.B
Apr 2 at 10:18
3
Also sometimes you can replace the non-free parts by free parts. The kind of thing that could be done in theory with some game engines in contrib and their assets (graphics, music...) in non-free or nowhere. The split made it clear it was possible to do this.
– A.B
Apr 2 at 10:31
add a comment |
Defined on the Debian Policy Manual:
2.2.2. The contrib archive area
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
Every package in contrib must comply with the DFSG.
In addition, the packages in contrib
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual.
Examples of packages which would be included in contrib are:
free packages which require contrib, non-free packages or packages which are not in our archive at all for compilation or execution, and
wrapper packages or other sorts of free accessories for non-free programs.
2.2.3. The non-free archive area
The non-free archive area contains supplemental packages intended to work with the Debian distribution that do not comply with the DFSG or have other problems that make their distribution problematic. They may not comply with all of the policy requirements in this manual due to restrictions on modifications or other limitations.
Packages must be placed in non-free if they are not compliant with the DFSG or are encumbered by patents or other legal issues that make their distribution problematic.
In addition, the packages in non-free
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual that it is
possible for them to meet.
Further reading:
Philosophy of the GNU Project
Categories of free and nonfree software
When Free Software Depends on Nonfree
Explaining Why We Don't Endorse Other Systems
add a comment |
https://www.debian.org/doc/debian-policy/ch-archive#s-contrib
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
This software could very well be software that is not available in main
despite being free. You just can't get it from debian.
It's not that you "cannot get it from Debian", it's just not part of the Debian distribution per se.
– Paradox
Apr 4 at 12:01
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509915%2fwhat-is-the-difference-between-contrib-and-non-free-packages-repositories%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
non-free packages are packages not complying to the Debian Free Software Guidelines definition. E.g.:
nvidia-driver
which provides a proprietary driver.
contrib packages are packages that do comply with the DFSG, but depend on non-free packages, or which depend on some non-free software downloaded (by the package or having to be downloaded manually) to work properly. So they don't end up in main
. E.g.:
bumblebee-nvidia
which while DFSG compliant, isn't really useful without the non-free package nvidia-driver
, so it's put in the contrib
section, or
vice
which requires to download (while respecting copyrights and laws) ROMs to work properly.
If somebody doesn't want to or can't use non-free software, that person most probably doesn't need or won't be able to use software depending on it, so it's more useful to put them separately in a contrib section. That person won't even have to download the contrib section.
UPDATE: the software in contrib, and its sources are still available for free use. Interesting parts could be reused in an other project, or the non-free (or non available) parts it depends upon could be replaced (e.g.: replace graphics, music etc. assets for a game engine in contrib). Having it separate from non-free helps to know which parts can be reused.
trivia: the Open Source Definition was initially created by removing any mention of Debian in DFSG.
2
I don't really understand the benefit to either Debian or its users of seperatingnon-free
andcontrib
. What is the actual advantage gained? As an end-user who doesn't care if a program contains non-free code, bothnon-free
andcontrib
are fine by me. As an end-user who does care, both are off-limits for me. What is the actual advantage?
– MechMK1
Apr 2 at 8:40
1
Like MechMK1, I am puzzled by this, and, even if I should have maybe have it written clearer in my question, that is also an aspect I would like to an answer to.
– Paradox
Apr 2 at 9:12
1
You can reuse and modify code from contrib to adapt it to an other project, because the source is available as any source from "main". You probably can't do this when it's from non-free, either the source licence doesn't let you do enough, or there is no source at all. If the end user is a "normal" end user who doesn't attempt to do anything beside what is distributed, I can imagine contrib and non-free would look the same
– A.B
Apr 2 at 10:18
3
Also sometimes you can replace the non-free parts by free parts. The kind of thing that could be done in theory with some game engines in contrib and their assets (graphics, music...) in non-free or nowhere. The split made it clear it was possible to do this.
– A.B
Apr 2 at 10:31
add a comment |
non-free packages are packages not complying to the Debian Free Software Guidelines definition. E.g.:
nvidia-driver
which provides a proprietary driver.
contrib packages are packages that do comply with the DFSG, but depend on non-free packages, or which depend on some non-free software downloaded (by the package or having to be downloaded manually) to work properly. So they don't end up in main
. E.g.:
bumblebee-nvidia
which while DFSG compliant, isn't really useful without the non-free package nvidia-driver
, so it's put in the contrib
section, or
vice
which requires to download (while respecting copyrights and laws) ROMs to work properly.
If somebody doesn't want to or can't use non-free software, that person most probably doesn't need or won't be able to use software depending on it, so it's more useful to put them separately in a contrib section. That person won't even have to download the contrib section.
UPDATE: the software in contrib, and its sources are still available for free use. Interesting parts could be reused in an other project, or the non-free (or non available) parts it depends upon could be replaced (e.g.: replace graphics, music etc. assets for a game engine in contrib). Having it separate from non-free helps to know which parts can be reused.
trivia: the Open Source Definition was initially created by removing any mention of Debian in DFSG.
2
I don't really understand the benefit to either Debian or its users of seperatingnon-free
andcontrib
. What is the actual advantage gained? As an end-user who doesn't care if a program contains non-free code, bothnon-free
andcontrib
are fine by me. As an end-user who does care, both are off-limits for me. What is the actual advantage?
– MechMK1
Apr 2 at 8:40
1
Like MechMK1, I am puzzled by this, and, even if I should have maybe have it written clearer in my question, that is also an aspect I would like to an answer to.
– Paradox
Apr 2 at 9:12
1
You can reuse and modify code from contrib to adapt it to an other project, because the source is available as any source from "main". You probably can't do this when it's from non-free, either the source licence doesn't let you do enough, or there is no source at all. If the end user is a "normal" end user who doesn't attempt to do anything beside what is distributed, I can imagine contrib and non-free would look the same
– A.B
Apr 2 at 10:18
3
Also sometimes you can replace the non-free parts by free parts. The kind of thing that could be done in theory with some game engines in contrib and their assets (graphics, music...) in non-free or nowhere. The split made it clear it was possible to do this.
– A.B
Apr 2 at 10:31
add a comment |
non-free packages are packages not complying to the Debian Free Software Guidelines definition. E.g.:
nvidia-driver
which provides a proprietary driver.
contrib packages are packages that do comply with the DFSG, but depend on non-free packages, or which depend on some non-free software downloaded (by the package or having to be downloaded manually) to work properly. So they don't end up in main
. E.g.:
bumblebee-nvidia
which while DFSG compliant, isn't really useful without the non-free package nvidia-driver
, so it's put in the contrib
section, or
vice
which requires to download (while respecting copyrights and laws) ROMs to work properly.
If somebody doesn't want to or can't use non-free software, that person most probably doesn't need or won't be able to use software depending on it, so it's more useful to put them separately in a contrib section. That person won't even have to download the contrib section.
UPDATE: the software in contrib, and its sources are still available for free use. Interesting parts could be reused in an other project, or the non-free (or non available) parts it depends upon could be replaced (e.g.: replace graphics, music etc. assets for a game engine in contrib). Having it separate from non-free helps to know which parts can be reused.
trivia: the Open Source Definition was initially created by removing any mention of Debian in DFSG.
non-free packages are packages not complying to the Debian Free Software Guidelines definition. E.g.:
nvidia-driver
which provides a proprietary driver.
contrib packages are packages that do comply with the DFSG, but depend on non-free packages, or which depend on some non-free software downloaded (by the package or having to be downloaded manually) to work properly. So they don't end up in main
. E.g.:
bumblebee-nvidia
which while DFSG compliant, isn't really useful without the non-free package nvidia-driver
, so it's put in the contrib
section, or
vice
which requires to download (while respecting copyrights and laws) ROMs to work properly.
If somebody doesn't want to or can't use non-free software, that person most probably doesn't need or won't be able to use software depending on it, so it's more useful to put them separately in a contrib section. That person won't even have to download the contrib section.
UPDATE: the software in contrib, and its sources are still available for free use. Interesting parts could be reused in an other project, or the non-free (or non available) parts it depends upon could be replaced (e.g.: replace graphics, music etc. assets for a game engine in contrib). Having it separate from non-free helps to know which parts can be reused.
trivia: the Open Source Definition was initially created by removing any mention of Debian in DFSG.
edited Apr 2 at 11:51
answered Apr 1 at 17:13
A.BA.B
6,17711131
6,17711131
2
I don't really understand the benefit to either Debian or its users of seperatingnon-free
andcontrib
. What is the actual advantage gained? As an end-user who doesn't care if a program contains non-free code, bothnon-free
andcontrib
are fine by me. As an end-user who does care, both are off-limits for me. What is the actual advantage?
– MechMK1
Apr 2 at 8:40
1
Like MechMK1, I am puzzled by this, and, even if I should have maybe have it written clearer in my question, that is also an aspect I would like to an answer to.
– Paradox
Apr 2 at 9:12
1
You can reuse and modify code from contrib to adapt it to an other project, because the source is available as any source from "main". You probably can't do this when it's from non-free, either the source licence doesn't let you do enough, or there is no source at all. If the end user is a "normal" end user who doesn't attempt to do anything beside what is distributed, I can imagine contrib and non-free would look the same
– A.B
Apr 2 at 10:18
3
Also sometimes you can replace the non-free parts by free parts. The kind of thing that could be done in theory with some game engines in contrib and their assets (graphics, music...) in non-free or nowhere. The split made it clear it was possible to do this.
– A.B
Apr 2 at 10:31
add a comment |
2
I don't really understand the benefit to either Debian or its users of seperatingnon-free
andcontrib
. What is the actual advantage gained? As an end-user who doesn't care if a program contains non-free code, bothnon-free
andcontrib
are fine by me. As an end-user who does care, both are off-limits for me. What is the actual advantage?
– MechMK1
Apr 2 at 8:40
1
Like MechMK1, I am puzzled by this, and, even if I should have maybe have it written clearer in my question, that is also an aspect I would like to an answer to.
– Paradox
Apr 2 at 9:12
1
You can reuse and modify code from contrib to adapt it to an other project, because the source is available as any source from "main". You probably can't do this when it's from non-free, either the source licence doesn't let you do enough, or there is no source at all. If the end user is a "normal" end user who doesn't attempt to do anything beside what is distributed, I can imagine contrib and non-free would look the same
– A.B
Apr 2 at 10:18
3
Also sometimes you can replace the non-free parts by free parts. The kind of thing that could be done in theory with some game engines in contrib and their assets (graphics, music...) in non-free or nowhere. The split made it clear it was possible to do this.
– A.B
Apr 2 at 10:31
2
2
I don't really understand the benefit to either Debian or its users of seperating
non-free
and contrib
. What is the actual advantage gained? As an end-user who doesn't care if a program contains non-free code, both non-free
and contrib
are fine by me. As an end-user who does care, both are off-limits for me. What is the actual advantage?– MechMK1
Apr 2 at 8:40
I don't really understand the benefit to either Debian or its users of seperating
non-free
and contrib
. What is the actual advantage gained? As an end-user who doesn't care if a program contains non-free code, both non-free
and contrib
are fine by me. As an end-user who does care, both are off-limits for me. What is the actual advantage?– MechMK1
Apr 2 at 8:40
1
1
Like MechMK1, I am puzzled by this, and, even if I should have maybe have it written clearer in my question, that is also an aspect I would like to an answer to.
– Paradox
Apr 2 at 9:12
Like MechMK1, I am puzzled by this, and, even if I should have maybe have it written clearer in my question, that is also an aspect I would like to an answer to.
– Paradox
Apr 2 at 9:12
1
1
You can reuse and modify code from contrib to adapt it to an other project, because the source is available as any source from "main". You probably can't do this when it's from non-free, either the source licence doesn't let you do enough, or there is no source at all. If the end user is a "normal" end user who doesn't attempt to do anything beside what is distributed, I can imagine contrib and non-free would look the same
– A.B
Apr 2 at 10:18
You can reuse and modify code from contrib to adapt it to an other project, because the source is available as any source from "main". You probably can't do this when it's from non-free, either the source licence doesn't let you do enough, or there is no source at all. If the end user is a "normal" end user who doesn't attempt to do anything beside what is distributed, I can imagine contrib and non-free would look the same
– A.B
Apr 2 at 10:18
3
3
Also sometimes you can replace the non-free parts by free parts. The kind of thing that could be done in theory with some game engines in contrib and their assets (graphics, music...) in non-free or nowhere. The split made it clear it was possible to do this.
– A.B
Apr 2 at 10:31
Also sometimes you can replace the non-free parts by free parts. The kind of thing that could be done in theory with some game engines in contrib and their assets (graphics, music...) in non-free or nowhere. The split made it clear it was possible to do this.
– A.B
Apr 2 at 10:31
add a comment |
Defined on the Debian Policy Manual:
2.2.2. The contrib archive area
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
Every package in contrib must comply with the DFSG.
In addition, the packages in contrib
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual.
Examples of packages which would be included in contrib are:
free packages which require contrib, non-free packages or packages which are not in our archive at all for compilation or execution, and
wrapper packages or other sorts of free accessories for non-free programs.
2.2.3. The non-free archive area
The non-free archive area contains supplemental packages intended to work with the Debian distribution that do not comply with the DFSG or have other problems that make their distribution problematic. They may not comply with all of the policy requirements in this manual due to restrictions on modifications or other limitations.
Packages must be placed in non-free if they are not compliant with the DFSG or are encumbered by patents or other legal issues that make their distribution problematic.
In addition, the packages in non-free
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual that it is
possible for them to meet.
Further reading:
Philosophy of the GNU Project
Categories of free and nonfree software
When Free Software Depends on Nonfree
Explaining Why We Don't Endorse Other Systems
add a comment |
Defined on the Debian Policy Manual:
2.2.2. The contrib archive area
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
Every package in contrib must comply with the DFSG.
In addition, the packages in contrib
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual.
Examples of packages which would be included in contrib are:
free packages which require contrib, non-free packages or packages which are not in our archive at all for compilation or execution, and
wrapper packages or other sorts of free accessories for non-free programs.
2.2.3. The non-free archive area
The non-free archive area contains supplemental packages intended to work with the Debian distribution that do not comply with the DFSG or have other problems that make their distribution problematic. They may not comply with all of the policy requirements in this manual due to restrictions on modifications or other limitations.
Packages must be placed in non-free if they are not compliant with the DFSG or are encumbered by patents or other legal issues that make their distribution problematic.
In addition, the packages in non-free
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual that it is
possible for them to meet.
Further reading:
Philosophy of the GNU Project
Categories of free and nonfree software
When Free Software Depends on Nonfree
Explaining Why We Don't Endorse Other Systems
add a comment |
Defined on the Debian Policy Manual:
2.2.2. The contrib archive area
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
Every package in contrib must comply with the DFSG.
In addition, the packages in contrib
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual.
Examples of packages which would be included in contrib are:
free packages which require contrib, non-free packages or packages which are not in our archive at all for compilation or execution, and
wrapper packages or other sorts of free accessories for non-free programs.
2.2.3. The non-free archive area
The non-free archive area contains supplemental packages intended to work with the Debian distribution that do not comply with the DFSG or have other problems that make their distribution problematic. They may not comply with all of the policy requirements in this manual due to restrictions on modifications or other limitations.
Packages must be placed in non-free if they are not compliant with the DFSG or are encumbered by patents or other legal issues that make their distribution problematic.
In addition, the packages in non-free
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual that it is
possible for them to meet.
Further reading:
Philosophy of the GNU Project
Categories of free and nonfree software
When Free Software Depends on Nonfree
Explaining Why We Don't Endorse Other Systems
Defined on the Debian Policy Manual:
2.2.2. The contrib archive area
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
Every package in contrib must comply with the DFSG.
In addition, the packages in contrib
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual.
Examples of packages which would be included in contrib are:
free packages which require contrib, non-free packages or packages which are not in our archive at all for compilation or execution, and
wrapper packages or other sorts of free accessories for non-free programs.
2.2.3. The non-free archive area
The non-free archive area contains supplemental packages intended to work with the Debian distribution that do not comply with the DFSG or have other problems that make their distribution problematic. They may not comply with all of the policy requirements in this manual due to restrictions on modifications or other limitations.
Packages must be placed in non-free if they are not compliant with the DFSG or are encumbered by patents or other legal issues that make their distribution problematic.
In addition, the packages in non-free
must not be so buggy that we refuse to support them, and
must meet all policy requirements presented in this manual that it is
possible for them to meet.
Further reading:
Philosophy of the GNU Project
Categories of free and nonfree software
When Free Software Depends on Nonfree
Explaining Why We Don't Endorse Other Systems
edited Apr 2 at 9:44
answered Apr 1 at 17:19
GAD3RGAD3R
28.3k1958114
28.3k1958114
add a comment |
add a comment |
https://www.debian.org/doc/debian-policy/ch-archive#s-contrib
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
This software could very well be software that is not available in main
despite being free. You just can't get it from debian.
It's not that you "cannot get it from Debian", it's just not part of the Debian distribution per se.
– Paradox
Apr 4 at 12:01
add a comment |
https://www.debian.org/doc/debian-policy/ch-archive#s-contrib
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
This software could very well be software that is not available in main
despite being free. You just can't get it from debian.
It's not that you "cannot get it from Debian", it's just not part of the Debian distribution per se.
– Paradox
Apr 4 at 12:01
add a comment |
https://www.debian.org/doc/debian-policy/ch-archive#s-contrib
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
This software could very well be software that is not available in main
despite being free. You just can't get it from debian.
https://www.debian.org/doc/debian-policy/ch-archive#s-contrib
The contrib archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function.
This software could very well be software that is not available in main
despite being free. You just can't get it from debian.
answered Apr 2 at 18:55
Malvin ButterfingerMalvin Butterfinger
1211
1211
It's not that you "cannot get it from Debian", it's just not part of the Debian distribution per se.
– Paradox
Apr 4 at 12:01
add a comment |
It's not that you "cannot get it from Debian", it's just not part of the Debian distribution per se.
– Paradox
Apr 4 at 12:01
It's not that you "cannot get it from Debian", it's just not part of the Debian distribution per se.
– Paradox
Apr 4 at 12:01
It's not that you "cannot get it from Debian", it's just not part of the Debian distribution per se.
– Paradox
Apr 4 at 12:01
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509915%2fwhat-is-the-difference-between-contrib-and-non-free-packages-repositories%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown