a pkgbuild this actually happens to would be usefull...

The function is "echo This is a statement" in this case.

And this is a problem because... ?

You should never need to rely on code that lives outside of a function.

Here's an example where I wrap it in a function...It has the same result.

but you are still calling the function outside of the predefined functions

Yeah, therein lies the problem. Why does makepkg run non-standard code twice? If I remove the call "dummy_echo", the function just doesn't run.

because it expects the users to follow the packaging guidelines?

and you shouldn't call these extra functions outside of build() prepare() or package() functions


https://wiki.archlinux.org/index.php/Arch_Packaging_Standards

I understand the guidelines, but it still seems like a glitch to me (makepkg running the same non-standard code twice).

Your opinion doesn't make this bug report useful. Presenting a valid use case where this legitimately breaks something, does.

Let's say as part of build process, some source code needs to be replaced (not patched, just replaced). Since all of this occurs before the build process, it is possible for the source code to be replaced twice.

Please provide a PKGBUILD. I have no idea what "replace the source code" means, or why you would need to do so.

Here's an example pkgbuild where I allow users to install additional language packs or help packs for libreoffice 4.0.

Yeah, let's not. Interactive PKGBUILDs are a totally braindead idea.

Why are they a braindead idea (since you said opinions don't matter)?

PKGBUILDs are meant to be a strict recipe. You run makepkg for a given input (a PKGBUILD) and get the same output (a package) every time. The packaging guidelines really should reflect this.

And as a user, I find it to be annoying as all hell.

I'll also add that there's nothing here you couldn't accomplish via split packages or stuffing your silly logic into the build function.

So how would you write a package that allows the user to install multiple language packs for libreoffice (other than creating dozens of PKGBUILDS).

And, how does this relate to the fact that makepkg runs non-standard functions in the PKGBUILD twice?

Build function occurs after source packages are downloaded. I did attempt such a method (using wget + tar) but ran into a fakeroot error.

> So how would you write a package that allows the user to install multiple language packs for libreoffice (other than creating dozens of PKGBUILDS).
With a split PKGBUILD. makepkg -i --pkg lang1,lang2,lang3

> And, how does this relate to the fact that makepkg runs non-standard functions in the PKGBUILD twice?
Let me be clear: The "bug" you're reporting is that makepkg sources the PKGBUILD twice. I really doubt this is "fixable".

I will look into split packaging, although I'm trying to reduce the lines of code and maintenance on my point (hence I don't want to write multiple package functions).

Is there a particular reason why makepkg sources the PKGBUILD twice?

Because it necessarily re-execs itself to run under fakeroot.

OK... look at the prepare function in pacman-4.1. Does what you want and lets us keep resourcing the PKGBUILD so we have the pkgname etc variables under fakeroot.