Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#22073 - makepkg command line option to build() (but not package())

Attached to Project: Pacman
Opened by Adrián Chaves Fernández (Gallaecio) - Sunday, 12 December 2010, 22:32 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 11:06 GMT
Task Type Feature Request
Category makepkg
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version 3.4.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Currently it is possible to repeat the package() function with ´makepkg -R´, without repeating the package() process.

I think in some (ok, very few) situations it might be useful to be able to do something different (not opposite, but kind of): just run the build process (so the package() one can be called later).
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 11:06 GMT
Reason for closing:  Won't implement
Comment by Dan McGee (toofishes) - Monday, 13 December 2010, 01:40 GMT
I hate theoretical bug reports. Give me an *actual* use case for this and maybe it will be obvious to the rest of us; until then this seems quite nonsensical.
Comment by Adrián Chaves Fernández (Gallaecio) - Monday, 13 December 2010, 02:10 GMT
The idea came to my mind in an actual case, of course. Not a common case, though.

I was running makepkg on a PKGBUILD for 0ad (it's available in AUR), and my computer freezed during the process. When I rebooted, I tryed running the process again from the begining (this time without kdm daemon running, from text mode to minimize processor usage, in case that were the reason of the previous freeze). I didn't know by then that the build process had gone successfully. I found out build process was successful, but during the XZ compression the system got into trouble (freeze again). I don't know what it was, but I believe it was no lack of either disk space or RAM.

When I (hard-)rebooted, I tried repackaging it (makepkg -R), and it worked. Later I ´makepkg´ed it again (for a independent repository with different versions of the dependencies) and run into troubles again, so my computer freezed and I had to hard-reboot and just ´makepkg -R´ it.

I could not have avoided it first time, but second time I would have just done the build step, the soft-reboot, and then ´makepkg -R´.
Comment by Adrián Chaves Fernández (Gallaecio) - Monday, 13 December 2010, 02:11 GMT
PS: I tried not to comment the actual case because it's somehow embarrasing :S
Comment by Allan McRae (Allan) - Sunday, 22 April 2012, 11:06 GMT
The use case here is essentially a work around for broken computers... which is not compelling to implement this. A workaround is to temporarily rename the package function. Closing as "Won't Implement".

Loading...