Re: How about sources.sources? (Was: Question Regarding sources.list)
On 5/24/20, Cindy Sue Causey <butterflybytes@gmail.com> wrote:
>
> PPPS Any outside 3rd party type packages that have been given
> permission to set up their own DOTlist files... will potentially
> complain that they can't find something or other yada. They're talking
> about how you may or may not now (?) have to delete DOTlist files for
> this TRICK (i.e. RADICAL.. COOL..) feature to work correctly.
>
> Their data can be worked right into that same lineup within that same
> single sources.sources file. Example:
>
> Types: deb
> URIs: https://deb.opera.com/opera-stable/
> Suites: stable
> Components: non-free
>
> CAVEAT: You MIGHT or MIGHT NOT still have to work through granting
> them permission via something like that curl/apt-key step. MAYBE. Time
> and case-by-case usage will tell..
Amending this part to mention that the referenced curl/apt-key step is
that one that helps verify the package's integrity before installing.
> PS to that as I look at that block: IF you use Bullseye non-free, that
> right there could possibly be combined into the same single block with
> your Bullseye data. I only use Bullseye main so that won't work for my
> own usage case.
Started playing with this again while waiting for a camera battery to
charge up. You can change the names AND have multiple different files
all ending with DOTsources. It's working the same way that it does
with DOTlist files.
My sources.sources is now momentarily renamed to debian.sources. Also
created a nonfree.sources and plugged that browser block above into
it. Ran "apt-get update" with no sources.sources file... no errors...
no balking. Yay!
#ThankYou to whichever Developers created that option. I really LOVE
that stacked way of cognitively picking out the details from each
block.
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *
Reply to: