You are not logged in.
Hello community,
I'm the maintainer of the speed-dreams-svn package (mainly for people that want to do some testing with SD's current SVN version, for everybody else the community package is better fitting). Unfortunately, the SVN tree is really huge in this case. I observed that after "make" the /tmp folder already eats up 6,7GB and should get even bigger when makepkg calls "make install". But I never came to this point, because my swap got full and my system froze... So I wonder whether there is any way to avoid this problem or the package should just be removed from AUR due to impracticability.
Thanks for any hint,
PhotonX
Last edited by PhotonX (2012-12-02 09:29:46)
Desktop: http://www.sysprofile.de/id15562, Arch Linux | Notebook: Thinkpad L13 Yoga Gen2, Manjaro
The very worst thing you can do with free software is to download it, see that it doesn't work for some reason, leave it, and tell your friends that it doesn't work. - Tuomas Lukka
Offline
Try to not use the /tmp folder.
Offline
Isn't makepkg using /tmp automatically? And if there is any possibility to change the folder, how to do so? I mean, after the installation (say, using some AUR helper) the build files should be removed, so using /tmp isn't such a bad idea...
Desktop: http://www.sysprofile.de/id15562, Arch Linux | Notebook: Thinkpad L13 Yoga Gen2, Manjaro
The very worst thing you can do with free software is to download it, see that it doesn't work for some reason, leave it, and tell your friends that it doesn't work. - Tuomas Lukka
Offline
I thought makepkg uses the current directory unless BUILDDIR is set in makepkg.conf. If that isn't the case then try setting BUILDDIR to something on a real disk.
I haven't touched it in ages so it may be broken, but take a look at svn-export. I think I wrote it for such situations where the full SVN history is ridiculously huge and completely unneeded for building the package.
Of course, if the 6.7 GB is only current data then it won't help.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
Isn't makepkg using /tmp automatically?
No, it uses the directory you run it in. Why do you think it uses /tmp?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Oh, my bad, actually I'm using yaourt and yaourt uses /tmp. With a direct makepkg call everything is fine. I suppose, from within yaourt there is no possibility to adjust the temp path?
Desktop: http://www.sysprofile.de/id15562, Arch Linux | Notebook: Thinkpad L13 Yoga Gen2, Manjaro
The very worst thing you can do with free software is to download it, see that it doesn't work for some reason, leave it, and tell your friends that it doesn't work. - Tuomas Lukka
Offline
man yaourt yaourtrc
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Thanks, but I meant kind of changing the path from within the PKGBUILD such that users of the package don't run into trouble like me.
Desktop: http://www.sysprofile.de/id15562, Arch Linux | Notebook: Thinkpad L13 Yoga Gen2, Manjaro
The very worst thing you can do with free software is to download it, see that it doesn't work for some reason, leave it, and tell your friends that it doesn't work. - Tuomas Lukka
Offline
The PKGBUILD should not contain local build info, just the recipe to build the package. Any configuration needed by the actual building mechanism on the local machine, should be configured in some config file on that machine.
Offline
This is true, but since this issue is only present in this specific package I cannot expect the users to care about the strange path configuration, I suppose...
Desktop: http://www.sysprofile.de/id15562, Arch Linux | Notebook: Thinkpad L13 Yoga Gen2, Manjaro
The very worst thing you can do with free software is to download it, see that it doesn't work for some reason, leave it, and tell your friends that it doesn't work. - Tuomas Lukka
Offline
We do expect people to have adequate settings for building any other package, don't we?
It would be terribly wrong to let infrastructural configurations mix up with the building recipe. I don't want this package to not build in ram on my supercomputer because your machine happens to not have enough ram, I want _my_ config to decide where to build it.
Offline
This is true, but since this issue is only present in this specific package I cannot expect the users to care about the strange path configuration, I suppose...
This is Arch. Users can be expected to deal with configuration files themselves when the need arises. I suggest that you simply add a message to the build function warning the user of the required size.
Besides, this is a yaourt issue as vanilla makepkg does not use /tmp by default. You should not add nasty hacks to PKGBUILDs to enable unofficial AUR helpers to manage edge cases.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
Thanks for your advice guys, I updated the package accordingly.
Desktop: http://www.sysprofile.de/id15562, Arch Linux | Notebook: Thinkpad L13 Yoga Gen2, Manjaro
The very worst thing you can do with free software is to download it, see that it doesn't work for some reason, leave it, and tell your friends that it doesn't work. - Tuomas Lukka
Offline