/tech/ - Technology

Sounds more like a problem with the thing you are trying to install. It's proprietary shitware.

I used Quartus II back in my digital electronics course in college. It was indeed a fucking monster that ate like 5 GB of disk space and that was 10 years ago, when 160 GB was pretty big for a hard disk. These massive disk usage stats are totally not surprising.

I don't think Arch devs are in charge of maintaining the user repositories anon.

>>545370

>the build system is the user repositories

>>545405

No?

>>545412

The build system builds things from the user repositories

>>545413

You mean makepkg? It's running a shell script provided by the person who maintains the packages, defining actions required to build it.

What does this have to do with the arch package format? As if it wouldn't be taking up all that space in an RPM spec file that defines the same thing.

You're retarded, retard.

>>545420

And yet gentoo has an ebuild which is a shell script that mysteriously doesn't take 52 gigabytes to do the same thing.

>>545443

The ebuild isn't creating a package, therefore it doesn't have to copy anything. It just has to run the setup file provided.

Why did you make this thread? Because you were too fucking stupid to read the PKGBUILD and ebuilds?

>>545454

Actually considering it merges to filesystem and then cleans up, it probably consumes the same amount of disk space. It's not creating a package though, unlike arch.

Can't you go shitpost elsewhere, like /g/? We already are slow enough with too many retarded fat fuck NEETs shitting up the board ironically.

>>545457

>Actually considering it merges to filesystem and then cleans up, it probably consumes the same amount of disk space.

That's weird, I don't seem to remember running out of hard drive space.

>>545461

Okay? The gentoo installation process should take up 38GB at some point.

Again, why did you create this thread?

>>545463

>The gentoo installation process should take up 38GB at some point.

What, did you calculate that?

>>545469

Pretty much common sense there. when it's finished merging to filesystem and before it cleans up the installation process will have taken up ~38GB.

>>545478

Surely it wouldn't need to take more than the size of the tar + the size of the tar once extracted, as the tar can only be deleted all at once.

>>545469

Portage creates a temporary image which is used to merge to the filesystem or can be used to create a binary package, dipshit.

>>545507

Quartus already is a binary package. The ebuild's locked to bindist.

>>545349

>when 160 GB was pretty big for a hard disk

and now it's 2016 and we have chromebooks with 16 GB SSDs

>>545363

>not using free open sauce ingredients