![]() In all other cases, they would create a new file in named exactly the way they wanted. The Google Chrome devs didn't check for the presence of Google Chrome sources, relying on the exact file name their Chrome package would create to be present. Sed -i '/.*some repo line for apt.*/d' /etc/apt/sources.list # deleting if commented out, thus respecting the user's wishes If \s*some repo line for apt' /etc/apt/sources.list ) ]] thenĮcho 'some repo line for apt' > /etc/apt/sources.list Also, unless they are checking ALL possible files, they can, and often do, add a duplicate item, which then makes apt complain, until you delete one of them.įor sources.list # to add. If they are doing the same check as below, then it's the same exact complexity, except carried out over many files, not one. Note that unless they are also doing the same check as below, if you had commented out a repo line, these tests would be wrong. If ] thenĮcho 'some repo line for apt' > /etc/apt//some_repo.list On a technical level, as someone who has had to handle these changes in a few large and popular system info tools, basically it comes down to this: Again, has to sed a directory instead of a single file. I do not understand this one, I "assume" package maintainer knows the URL of his repository. It allows a package maintainer to give a simple command to update repository locations without having to worry about inadvertently changing the configuration for unrelated repositories. It allows a system administrator to easily disable (by renaming) or remove (by deleting) a repository set without having to edit a monolithic file.Īdmin has to grep directory to find appropriate file to rename, before, he would search ONE file and comment out a line, a sed one-liner for "almost" any admin. Unless they assume admin's don't change things. ![]() Now, they have to search a directory for dupe's instead of a flat file. It allows new installations that need their own repos to not have to search a flat file to ensure that it is not adding duplicate entries. I must add, I love change, however, ONLY when there are benefits introduced by the change. 1 still beats 2).Ĭan somebody please come up with a rational advantage, "you can clearly see custom additions" is a poor man's excuse. Means I have half a dozen files to parse instead of just one.ĪFAIK, there is "absolutely" no advantage in having one configuration file vs 6 (for sake of argument, maybe you have 3 or even 2, doesn't matter. When I add ppa's (which I have not done in years), I hit a key on my keyboard labeled "Enter" which allows me to add an empty line before the new entry (I would even add an explanatory comment, but I am a tech writer, so. I know this question has been asked before, but I do not accept the answer, "you can clearly see custom additions".
0 Comments
Leave a Reply. |