FS#17068 - [makepkg] Check if -e $pkgdir

Attached to Project: Pacman
Opened by Gavin Bisesi (Daenyth) - Sunday, 08 November 2009, 20:54 GMT
Last edited by Allan McRae (Allan) - Monday, 09 November 2009, 02:21 GMT
Task Type Bug Report
Category makepkg
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version git
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If $pkgdir is empty, makepkg should not create a package from it.

Too much $other_project state in my head to code it in at the moment, but it should just be a "[ -e "$pkgdir" ] && exit_with_error" or something like that.
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 09 November 2009, 02:21 GMT
Reason for closing:  Won't implement
Additional comments about closing:  See comments
Comment by xduugu (xduugu) - Sunday, 08 November 2009, 21:52 GMT
Could you explain why do you think this is necessary/useful? It would remove the possibility to create metapackages.

By the way, -e $pkgdir only checks if $pkgdir exists.
Comment by Allan McRae (Allan) - Sunday, 08 November 2009, 23:40 GMT
I agree. Empty packages are useful.
Comment by Gavin Bisesi (Daenyth) - Monday, 09 November 2009, 01:34 GMT
You're right xduugu about the -e check being wrong, that would be something else. I also forgot about meta packages, but I thought we more or less tried to avoid those in favor of groups?

I'll leave it to your discretion. For me it would be useful, but the metapackage aspect I hadn't considered.
Comment by Allan McRae (Allan) - Monday, 09 November 2009, 02:20 GMT
Groups are favourable over meta-packages only if you control the repos. Another use case is fooling pacman that a dep is installed when nothing else provides it.

So this is going to be a Won't Fix.

Loading...