FS#71376 - Support local folders in sources

Attached to Project: Pacman
Opened by Hunter Wittenborn (hwittenborn) - Monday, 28 June 2021, 00:39 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 28 June 2021, 01:54 GMT
Task Type Feature Request
Category makepkg
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 6.0.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I currently use makepkg to create and test some packages I use locally, but doing so with makepkg is currently quite a pain when a project contains a lot of files.

Currently, I'm using a `git+file://${PWD}` method that works for the most part, but it requires me to make relatively useless commits just for the sake of testing.

It would be really nice if I could just enter something like `file://${PWD}`, and then makepkg could just detect if it's a folder, and if so, just copy the folder over into $srcdir.
This task depends upon

Comment by Eli Schwartz (eschwartz) - Monday, 28 June 2021, 01:54 GMT
  • Field changed: Attached to Project (Arch Linux → Pacman)
  • Field changed: Summary ([pacman] Support local folders in makepkg → Support local folders in makepkg)
Moving to the pacman bugtracker.
Comment by Eli Schwartz (eschwartz) - Monday, 28 June 2021, 01:56 GMT
I think this is basically FS#43020?
Comment by Hunter Wittenborn (hwittenborn) - Monday, 28 June 2021, 13:57 GMT
Most of the same things apply, yeah.

I don't think I mentioned it, but when I enter something like `file://${PWD}`, it adds it into $srcdir, but it creates something that resembles a file. My terminal is giving it a special color different from folders and normal files though, so I'm thinking makepkg might be trying to do something weird with it.
Comment by Eli Schwartz (eschwartz) - Monday, 28 June 2021, 14:40 GMT
file:// is a remote download url that happens to be implemented via the curl download agent. For local sources you just don't include a URI protocol and makepkg expects to either find it in $PWD or $SRCDEST, or else it fails with an error that it's invalid to try to download it.

All sources (other than VCS clones) regardless of how they are acquired are always symlinked one by one into the $srcdir. It's not weird.
Comment by Hunter Wittenborn (hwittenborn) - Monday, 28 June 2021, 21:35 GMT
Makes sense, that's my bad.

Regardless, even something like "path/to/folder" would help greatly, even if required to be relative to the PKGBUILD's path.

At that point then it's pretty much completely like the other issue though.

Loading...