Pacseek - A terminal user interface for searching and installing Arch Linux packages

General system Community contributions
101

Sorry. No plans for flatpak support.

5 Likes
102

Well, hey, at least it’s terminal-centric. :wink:

103

There are times when I’ll grab a flatpak over the AUR option, it’s dependent on versioning and whether the AUR version compliles or is orphaned, etc etc. Sometimes it’s nice to be able to see both side by side. But I can understand the author wanting to keep the utility simple.

1 Like
104

its a personal project also hard to maintain, best is to do best… keep track you need atleast few others

1 Like
105

@moson

:pray: for this . think it wonderful you add colours :pray: it just take time remember it installed . brain need changing from pacman/yay -Ss (pkg)

little colour change , now it match my system

Pacseek-idea

Thank you…

6 Likes
106

Those are pretty solid and easily readable colors, mind sharing how you added them exactly (like the color/hex codes)? Thanks

107

NP.

{
	"Accent": "616e87",
	"Title": "dc8cc3",
	"SearchBar": "4b728c",
	"PackagelistSourceRepository": "8c8db9",
	"PackagelistSourceAUR": "8cd0d3",
	"PackagelistHeader": "f0dfaf",
	"SettingsFieldBackground": "6092b4",
	"SettingsFieldText": "dcdcdc",
	"SettingsFieldLabel": "dfaf8f",
	"SettingsDropdownNotSelected": "66678b"
}
4 Likes
108

I should probably emphasise that I DO like it. Even though it doesn’t really fit my workflow 100%, I think it’s a good option for others, and I hope the EndeavourOS project considers adopting it. And I’m still going to install it and take it for a spin sometimes, even if it won’t be my main solution. :slight_smile:

109

What do you mean by adoption? @moson is already developing and maintaining it.

110

It’s in the AUR for now. I assume if Endeavour adopts it it would end up in the EndeavourOS repos? Maybe I’m wrong?

1 Like
111

Why hide it in the EnOS repos? If enough people will use it, it will make it into arch community repos for every arch based distro.

4 Likes
112

Why not both?

113

Because it’s not really necessary. Flip side, it would shut up all the stupid requests for an app manager.

That alone is worth it actually. Ship it.

5 Likes
114

New version 1.5.1 is out.

New stuff
  • PKGBUILD file can now be opened within pacseek itself.
    • It has syntax highlighting and adapts to the selected color scheme.
    • Selecting “Custom” color scheme also allows to override the style:
{
	"Accent": "1793d1",
	"Title": "00dfff",
	"SearchBar": "0564a0",
	"PackagelistSourceRepository": "00b000",
	"PackagelistSourceAUR": "1793d1",
	"PackagelistHeader": "ffff00",
	"SettingsFieldBackground": "0564a0",
	"SettingsFieldText": "ffffff",
	"SettingsFieldLabel": "ffff00",
	"SettingsDropdownNotSelected": "0564a0",
	"StylePKGBUILD": "dracula",
	"Comments": "Examples for StylePKGBUILD can be found here: https://xyproto.github.io/splash/docs/all.html"
}

image

19 Likes
115

Now that this can actually view PKGBUILDS I think I’m replacing pamac with this. Nice thing, It can integrate with the Arch updates plugin for GNOME pretty well, though I just have the plugin launch “yay” directly for updates). Besides, the few flatpaks I do have installed hardly ever update anyway, so I really don’t need to be checking them as much.

Only problem with this setup is that it doesn’t check the AUR for updates, but yay will update the AUR pacages when it processes the repo updates. Or I could just have it it notify me about updates, and launch pacseek at the available updates dialog, is that possible with a flag?

image

116

No clue what the “available updates dialog” is, but when you want to update your system, simply run yay :person_shrugging:

2 Likes
117

I was thinking I might like to browse the available updates and look at the PKGBUILD files for any AUR updates first. I’m guessing there’s no way for pacseek to show a list of the packages that have an update available either? Not a big deal if not, just thinking it would be nice to see a list of pending AUR updates before running them.

118

Currently not. And I’m not sure how much sense that would make:

When you run yay it’ll tell you what’s there to upgrade + you get the option to review the PKGBUILD diff’s as well. You can still bail out from upgrading at that point as well.

1 Like
119

The sense would be to look at the PKGBUILD files before kicking off the update. One might decide not to update, or only update (or just “reinstall” I guess) certain AUR packages and skip the ones where they don’t trust the PKGBUILD file. With yay, you have to bail out entirely and start over each time you hit a PKGBUILD you decide you don’t like or want to skip.

Of course, that would mean either putting in some logic in the upgrade command or running a “yay ” etc for each AUR update (and a "sudo pacman -Syu for the package updates) rather than just a “yay” for everything, so it might be a little harder to implement.

120

The case where you start “not trusting a PKGBUILD anymore” in case of an update for an already installed package is extremely rare I’d say. (at least I’ve never encountered that case so far)

You might want create a issue/feature-request over at the yay github page. :wink:

It’s somewhat of a “toy functionality” which nobody really needs but it’s just nice to have regardless.
But who knows. You might see it getting implemented some day (I’m usually prone to those kind of things too). :slight_smile:

2 Likes