User talk:Scimmia

Changes in grub regarding addition of '/boot' to configuration files.

When you reverted my changes, you mentioned "This isn't a 'keyword', it's part of the path, which is relative to the volume it's on. This is already explained above when set root= is mentioned." I agree with the correction on the keyword part but where is the explanation you mentioned? Ic ouldn't find it.

As I said, it's when you 'set root='. Specifically when it says "set root=(hdX,Y) sets the boot partition, where the kernel and GRUB modules are stored (boot need not be a separate partition, and may simply be a directory under the "root" partition (/)" As that's the partition you're working on, paths are pretty much common sense from there.

If common sense is considered, the Arch wiki would be much shorter. But then again what seems like commmon sense to us might not be for new users. In the GRUB wiki page itself under, Encrypted_/boot, the tip I mentioned regarding /boot in path is mentioned. But I suggest to add it in more places especially tthe Custom_grub.cfg section becuase incorrect configuration will lead to unbootable systems. --RaZorr (talk) 05:40, 25 March 2022 (UTC)

No, the tip you mentioned regarding /boot is NOT in the Encrypted_/boot section.

You keep saying how this could lead to an unbootable system; yeah, so what? If you screw up a config, it doesn't work, that's pretty normal and this situation is not special.

If you want to expand the 'set root=' part a bit and say that all paths are relative to this, that can make sense. The tip as you had it did not.

Scimmia (talk) 12:11, 25 March 2022 (UTC)

The section I was talking about was wrong. Sorry for that. The actual one is this GRUB#Using_the_rescue_console. This has multiple notes on the /boot prefix. Expanding the 'set root=' part and saying about relative paths is a relatively complicated way of saying the same thing as the tip/note I had provided. So, it doesn't really make any sense and I would rather avoid that. --RaZorr (talk) 12:27, 25 March 2022 (UTC)

GRUB

There are no instructions at all that really document how to setup Secure Boot with GRUB and verified initrds, so I thought that at least some third-party instructions would be nice (even if they don't work). I wanted to add this note as a warning for other people so they don't even start the instructions on that website (because they will inevitably fail). The instructions on that Third-party page have a lot to do with the Wiki page: they are about GRUB as well. I don't think it's fair that you removed my paragraph. Could you maybe re-include it, please? DasMenschy (talk) 14:17, 22 September 2022 (UTC)

VCS package guidelines

Let's go over what you reverted.

You say these were material changes, "most of which" were incorrect.

I am very interested to hear what you believe to be incorrect. quequotion (talk) 13:57, 10 January 2023 (UTC)

Sure. First off, the pkgbase doesn't really matter, the pkgname is what's important, so that change was incorrect.

Second, the pkgver/pkgrel thing is for *any* change that changes the end package, which is what the original text states. Changing 'any' to a list, even as examples, is incorrect.

Third, you need to include anything it conflicts with or provides, not just the non-vcs version.

Forth, replaces doesn't really do much in the AUR. It only works with binary repos, and it's only really for things like project name changes. It's not just about things removed from the AUR.

Scimmia (talk) 23:40, 10 January 2023 (UTC)

First, pkgbase matters when it's a split package that will create multiple *-git packages to be installed, and is interchangable with pkgname for an ordinary package. I find pkgbase to be the better convention.

Second, So why did you revert from "any" as I put it, back to the list you find incorrect? Yes, you did the opposite of what you are talking about.

Third, that is true, but that is not what this section is about. Consider the point of view of someone who has never done this before: they may need to be reminded to include the usual conflicts and the repository version of the package in addition, which is what this section is trying to communicate. I think there may be a more optimal compromise, but "what" as a demonstrative pronoun is not it.

Fourth, I was expecting that response. It sounds like you intend to split the PKGBUILD specification into two standards: one for repositories where certain components matter, and one for elsewhere where they don't. That's not a good idea, that's just confusing. In addition, did you actually read what you reverted? I made it very clear the purpose of replaces is deprecation, ie when a project name has changed. I did mention the old one may be deleted from the AUR, but I don't think the way I put it would imply that using replaces is contingent on deleting anything from the AUR. The cryptic warning kind of invites people to play with it to find out what it does. An alternative here would be to remove this point altogether, or simplify the warning to something more constructive and link to the appropriate section on PKGBUILD's page. quequotion (talk) 08:29, 11 January 2023 (UTC)

For number 2, you're right, I read it wrong and that was not the reason I had a problem with that change originally. Saying that increading the pkgrel is mandatory is flat out wrong. The rest of what I said stand, but if you're wanting a debate instead of just an explaination, this should be on the talk page for the page in question, not here. Scimmia (talk) 10:31, 11 January 2023 (UTC)

I will happily open a new discussion there shortly, but you should know it already happened. It had been open since March 2019 and you chose not to participate in it. I closed it in December 2022 when its primary objective (restructuring the bulleted lists as subsections) was completed.

All of the changes already had (minimal) consensus, but I made the decision to save the cosmetics for later in anticipation of this conversation.

That is to say, sure, let's have that discussion again, but actually have it this time--because I do want a debate: I have always wanted a debate. quequotion (talk) 12:48, 11 January 2023 (UTC)