Skip to content

Conversation

@sharkwouter
Copy link
Member

I've tested this on Arch and Debian. It didn't seem to cause any issues for me.

@sharkwouter
Copy link
Member Author

Closes #11

@sharkwouter
Copy link
Member Author

Makepkg does actually use pacman-conf, though, although I'm not sure for what. This will return the wrong paths if pspdev had been moved. I'm not sure if this is a problem, I'll try to figure it out from the code.

@sharkwouter
Copy link
Member Author

An update, I just checked. Makepkg only uses pacman-conf to check where the lockfile is. It only checks if the file exists (which it won't if PSPDEV is in a different location), but since pacman also checks for it, it should be fine if the check doesn't work. We could probably patch the check out.

@sharkwouter
Copy link
Member Author

I did some additional testing based on your suggestions and I'd say we should either leave this as is or patch pacman a bit more. I think the wrapper script using some extra flags is probably preferred over increasing the amount of changes we make, but I'll leave that up to you @carstene1ns

The previous solution was better, but doesn't work on Mac because of a
bash version which is too old.
@sharkwouter
Copy link
Member Author

Okay, I've made some changes to prevent the issue on Mac and to prevent an issue when using sudo. It is not the cleanest solution, but it does work well and it should no longer be broken on Mac.

@sharkwouter
Copy link
Member Author

Since the progress on Clang seems to have slowed down, we should probably see if we can merge this and with the rest of psp-pacman.

@wally4000
Copy link
Contributor

I don't see any issues in adding psp-pacman to the repo, anyone else care to comment?

@carstene1ns
Copy link
Member

Currently it brings no real improvements as all libraries are still built on each developer's machines. There are some open tasks yet. (e.g. repo)

@sharkwouter
Copy link
Member Author

While it doesn't offer a big benefit yet to include it in the toolchain, this particular PR does not make it to it is part of it. I'm working on a way for us to set up a repo. I have a small scale prototype up here: https://github.com/sharkwouter/arch-repo-test

We may be able to use a release on Github as a repository, but I'm not sure how many packages you could add to a release. Otherwise we could use S3, but that's only free for a year unfortunately, although not expensive.

@sharkwouter
Copy link
Member Author

To clarify why this PR is still here and still needed. This PR simplifies psp-pacman and the scripts surrounding it and fixes the following issues:

@John-K John-K self-requested a review August 28, 2021 04:29
Copy link
Member

@John-K John-K left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine, we should merge this and get this in the toolchain

@sharkwouter sharkwouter merged commit ba17b55 into master Aug 28, 2021
@sharkwouter sharkwouter deleted the no-system-pacman branch August 28, 2021 09:23
@sharkwouter
Copy link
Member Author

Thanks @John-K, that made me able to merge this.

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

Successfully merging this pull request may close these issues.

5 participants