Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download everything and ask all the questions first, then build and install #27

Closed
maximbaz opened this issue Jun 11, 2017 · 9 comments
Closed

Comments

@maximbaz
Copy link
Contributor

I saw you have this on the projects page, I'm creating this issue for tracking purposes, something to subscribe to, in order to get updates when this works begins.

When installing or upgrading packages, it would be really nice to get all the questions asked first (do I want to edit PKGBUILD, install dependencies, confirm conflicting package replacement, etc.), answer to all of them in one go and let the installation proceed without further interruption.

@Jguer
Copy link
Owner

Jguer commented Jun 14, 2017

Yes, I wanted to get that working before releasing yay v2 but exam season hit a little earlier than expected.

  • Ask all edit PKGBUILD
  • Install all dependencies (Package conflicts are all handled by pacman I think)
  • AUR dependencies are installed with --noconfirm on pacman but
  • final built packages are moved to ${yay-build-dir} and one last confirm to install them all.

@rmarquis
Copy link

(Package conflicts are all handled by pacman I think)

Unfortunately, you'll have to handle this by yourself then bypass pacman prompts if you want to ask all the questions first - otherwise you'll have to deal with a yaourt-kind of linear prompts through the whole building process.

@AladW
Copy link
Contributor

AladW commented Dec 17, 2017

Even if you ask all questions first, you might have to confirm 100's of times on large dependency chains. Some better approach is to have the user deal with it (by having a "download only" stage, see trizen/trizen#8) or integrate with a suitable file manager.

Also the issue with conflicts pretty much disappears when you use a local repo (I've hardly seen them building 2000+ packages anyway), but I guess that's out of scope for this issue.

@maximbaz
Copy link
Contributor Author

True, although in my personal experience I haven't seen such long dependency chains, I think in 99% of cases you don't need to confirm more than 10 packages at once, and having an integrated approach to answer up to 10 questions and let yay proceed would be very useful 🙂

@132ikl
Copy link

132ikl commented Dec 22, 2017

Any ETA on this? Liking yay as an alternative to the now unmaintained pacaur but this is definitely my biggest issue with yay.

@Mayurifag
Copy link

+1 here.

Also, sorry for offtopic, but is there any way to list searched packages the same way like it was in yaourt — I meant, starting from first number and list all them from top to bottom?

@maximbaz
Copy link
Contributor Author

maximbaz commented Jan 6, 2018

@Mayurifag if you still seek the answer to the offtopic question: --topdown will change the sorting order, and since #83 the numbering always starts from 1 (not released yet, only in master).

@Mayurifag
Copy link

@maximbaz can i default --topdown behaviour in configuration file?

@maximbaz
Copy link
Contributor Author

maximbaz commented Jan 7, 2018

Yes, actually because --topdown is listed in the Permanent configuration options section of the $ yay --help, after you use --topdown at least once, yay automatically updates the config and --topdown becomes default for plain yay - that is, until you explicitly use --bottomup.

In the ~/.config/yay/config.json the --topdown refers to sortmode: 1, while --bottomup refers to sortmode: 0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants