User talk:Quequotion/Arch User Repository

From ArchWiki
Jump to navigation Jump to search

Breakdown of changes

I've been told my changes are hard to follow, and this--in part--led to the reversion of several months' work on the AUR page and splitting half of it into a protected page. I will try here to describe the changes as best I can. Nonetheless, if you are looking to compare the draft to the current page that is what you should do; rather than digging through edit histories, compare the two at their current state (just like you would two drafts of a physical document), and leave feedback from this comparison.

As some changes depend on others, this breakdown will be in the order such changes are intended to be made.

Not that this page is nearly out of active discussions, I'd like to focus on how, and when the remaining changes, which are dependent on changes to AUR submission guidelines are to be made. quequotion (talk) 18:35, 23 August 2020 (UTC)


Most of these changes are to reduce FAQ answers to the shortest possible statements with links to appropriate tutorials and information elsewhere. Much of their of content is duplicated from pages like PKGBUILD and Makepkg; some FAQs sequester information that should have a relevant section on either the User:Quequotion/Arch User Repository or User:Quequotion/AUR submission guidelines pages.

Since there's been no valid dispute of the proposals for "What is the AUR?" or "How do I create a PKGBUILD?", I'll go ahead with those changes in July. Once again, I do understand that a lack of disapproval does not equate to approval. I have given more than enough time under any circumstances for these changes to be discussed. quequotion (talk) 16:39, 3 June 2020 (UTC)

What is a Trusted User (TU)?

It isn't necessary to explain in so much detail here, as this FAQ already links to pages with more details. Furthermore, I'd rather use a different format for the title of this FAQ. See Special:Diff/574544

Removing the reference to [community] is not that helpful: it is central to an understanding of the TU role. Jasonwryan (talk) 20:58, 21 July 2019 (UTC)
There is still a link to the community repository page in a sentence that describes the TU role in that repository. Is this insufficient? quequotion (talk) 02:38, 22 July 2019 (UTC)
It is not as clear that they are responsible for [community] as well is what I meant (and expressed badly). Jasonwryan (talk) 02:41, 22 July 2019 (UTC)
I see what you mean, and have reworded to clarify the two-fold role TUs play in community. quequotion (talk) 06:41, 22 July 2019 (UTC)
Looks OK to me, but a TU should make the final call (on most of these changes, really). Jasonwryan (talk) 07:01, 22 July 2019 (UTC)
Considering how much hounding, hassling, and time it took to get this review, moving the goalpost that far out of field will likely delay this several years. I think your approval is consensus enough, but I will allow one more week for refutation before I implement this change. quequotion (talk) 15:36, 24 August 2019 (UTC)
The original revision is definitely not perfect. The proposed one, however, only removes details (like "popular" AUR packages constitute the majority of community packages by definition) and tacks on a second "also" sentence because the first did not suffice.
I'm also tired of your melodrama and suggest you leave it at home. -- Alad (talk) 17:15, 24 August 2019 (UTC)
How about this version? The issue with the "also" part, (now "as well as") is trying to express the three aspects of their role in one sentence with sound grammar: to say they oversee the AUR and community, in addition to saying they maintain community packages, without accidentally implying that they maintain packages in AUR.
The original version of this used the word "popular" to describe the packages in community without explaining that it meant popular AUR packages promoted to community, besides which, the detail is extraneous: what this FAQ should do is identify the TUs, as breifly as possible explaining what they do, linking to details elsewhere.
See User:Quequotion/AUR submission guidelines#Promoting packages to the community repository for a more appropriate subsection dedicated to explaining how AUR packages may enter community, and User_talk:Quequotion/AUR submission guidelines#Promoting packages to the community repository to discuss it. quequotion (talk) 19:19, 24 August 2019 (UTC)

Installing packages

I understand that this change was cited in the discussion that precipitated the reversion for removing "The AUR is unsupported".

As noted by Alad above, the unsupported status of AUR packages should be well established in readers' minds by this point.

This warning creates ambiguity about pacman. The (technical) reason pacman does not get AUR updates is not because AUR is unsupported, but because pacman can only interface with repositories of prebuilt packages--including unsupported, third-party repositories. My rewording was intended to clarify that pacman is not capable of discovering AUR package updates, and it still states that it is the user's responsibility to check for them.