Silly Vpackager (building packages) question

[nitehawk]

Just wondered as to how LONG it is supposed to take for the vpackager to build a package, AFTER it's downloaded?  I know wine is a large package,....I downloaded it (the files or what-ever),...but when it came time to BUILD the wine program,....it took HOURS before I finally just aborted the thing.  Tried again the next day,...the same thing.   Tried a smaller package,...and it also started taking forever.  After 2 hours of watching it "build",...I switched it off.  (?)   I can see in the "window" of the vpackager that it is actually really doing something (not just hung-up).  What's the deal there?  I admit I'm a tad disappointed in the extreme amount of time that seems to be required.

[M-ake]

Well generally a compiling process/package creation time is determined by your computer's specs.

Oh those good ol' days when I used to compile wine on my p3 550 Mhz box<3.

[lagagnon]

There either is a problem with your gcc compiler setup (have you done any recent upgrades?) or your computer is incredibly slow and low and RAM. Please tell us about your machine first and the output of "gcc --version"...

[M0E-lnx]

When vpackager builds a package for you, all it does it automate the steps you would have to take if you were doing it manually.
With that said, it is not intended to make your build times any shorter at all.

Some packages will take literally hours to build (For instance, try building KDE4 on a 1.5ghz CPU and let me know if you can do it within 3 hours )

My point is, the time it takes to build a package only changes with the cpu speed or some flags parsed to the make process (which vpackages does not do because 7/10 times results in a failing build)

If vpackager has not hung on you, that means it's doing it's job, it's just the package taking forever to build.

[nitehawk]

OK,...it's probably that I can't really build packages in Vector with this machine (P3 384ram 500mhz 8g hd)  I've been able to do it in other distros,....but Vector is a bit different,...(I'm disappointed)  alas.

[kc1di]

When I recently built wine mannually it took about 1 hour. 
I have built wine 0.9.60 it should be moved to the test repro soon.
Cheers! Dave

[M0E-lnx]

OK,...it's probably that I can't really build packages in Vector with this machine (P3 384ram 500mhz 8g hd)  I've been able to do it in other distros,....but Vector is a bit different,...(I'm disappointed)  alas.

Let's face it, your hardware is not ideal for building packages in a timely manner.
Not that you can't do it, it just will take long becuase your processor speed is slow and the package you're building requires a lot.

[nitehawk]

OK,...thought I'd best post a bit of an update,...............
got discouraged because Vector's vpackager was taking sooooo long on my old machine  (that I affectionately named "Scrapmetal").   I know that Vector really runs nice on it, though,...so the update to all of this, is that I am busy re-building another computer I have,  just for Vector.  Still not going  to be a brand-new "whiz-bang".....but will be faster than this one.    Got the motherboard coming in today (or tomorrow) it'll be twice as fast as this old 500mhz.  (Well,..Almost...it'll be 933mhz).............should help with the vpackager just a tad.   But actually,....I shouldn't be needing THAT many different apps,..since Vector is pretty complete for me as is.    Nice distro.   Brand-new to linux and started out with Puppy linux.  That's a super nice distro,...but things like Firefox browser don't seem to be the latest,  like Vector has.   Besides, I wanted a bit of a more "serious" distro, without all that extra bloat that the big distros have.   Vector will work just fine.

[kc1di]

Think it will work really well for you on the 933MHZ..  Try to get as much ram as you can though.
Cheers!
dave