64bit livecd?

[Neal ManBear]

@Neal: Any tips on packaging issues for helping with 64-bit packages?

Galen

Dependencies. In some cases, I have been unable to package an app due to its build dependencies being not yet available. In such cases, you try to package what is needed, of course. Sometimes you may find that the package you have just built is not installable due to missing dependencies.
Forging ahead is the only way, IMO. The more new packages that get built and added, the easier the packaging will become.     
Also, pkgutils are not yet available for 64-bit. You will need to do it manually.     

Are there any changes for 64bit in the spec files, or does building in a 64bit environment automatically take care of the 64bit build process?

Galen

You need to check the BuildRequires and Requires in the spec against what is available in the 64-bit repo. For example, libgtk+2.0_0 is lib64gtk+2.0_0 for 64-bit. Some dependencies may not have this change. You have to check to see what you need to change.     

[gseaman]

Thanks!

Galen

[HawkEye4077]

<snip>
Back up your personal files, as you will need to format your /home partition.     

Other than the likes of KDE or Gnome config files why do you need to format your /home directory ?

Unless this has to be hard coded for some specific issue I can't think of a reason as to why this should have to be done.  If it is just the config files then deleting things like .kde should be sufficient.

Note that I don't have an issue with doing it I would just like to understand why.

[T6]

i was thinking that

 i don't use /home partition so for me it is something basic to backup when reinstalling

[Neal ManBear]

<snip>
Back up your personal files, as you will need to format your /home partition.     

Other than the likes of KDE or Gnome config files why do you need to format your /home directory ?

Unless this has to be hard coded for some specific issue I can't think of a reason as to why this should have to be done.  If it is just the config files then deleting things like .kde should be sufficient.

Note that I don't have an issue with doing it I would just like to understand why.

You would need to delete every hidden file and folder in your /home/<you>. Be sure you do not miss anything. Even then, you may not have any success, as the 64-bit filesystem, of which /home is a part, is not exactly the same as the 32-bit filesystem.     

That is my understanding of it.     

[T6]

afik, the ext4 partition has no relation with the os in use

now, don't know about reiser and other popular filesystems

the partition limits itself to follow the orders given by the os and the popular partitions we use on linux are extremely capable, especially ext4

the 64 bit commands implies differences in how the ram is used and maybe swap

[Neal ManBear]

afik, the ext4 partition has no relation with the os in use

now, don't know about reiser and other popular filesystems

the partition limits itself to follow the orders given by the os and the popular partitions we use on linux are extremely capable, especially ext4

the 64 bit commands implies differences in how the ram is used and maybe swap

I was speaking of the Linux filesystem, not the partition filesystem. / and every directory in it is the Linux filesystem.     

[T6]

in my original post, i was talking about / too, it is necessary to format it

[Neal ManBear]

in my original post, i was talking about / too, it is necessary to format it

You get no disagreement from me about that.

[HawkEye4077]

OK think I understand that. For me there would be less problems as I am currently using an x64 Fedora system so my /home drive should be fine.

I would probably still backup and format to be safe anyway but theoretically I could get away with not doing it.

Thanks for the response folks.

[Neal ManBear]

OK think I understand that. For me there would be less problems as I am currently using an x64 Fedora system so my /home drive should be fine.

I would probably still backup and format to be safe anyway but theoretically I could get away with not doing it.

I think you may be quite likely to have a problem, if you use a /home set up by fedora for your PCLinuxOS /home. There are enough differences between the 2 distros that you most likely will get some serious difficulties because of it.
You'll do as you please, of course, but I'm going on record here in advising against it. Do your backup and format your /home partition as well as your / partition.       

Thanks for the response folks.

     

[T6]

yes, most users want to share /home partition with other distros installed on their hard disk

i find this a source of problems for those reasons mentioned by Neal

some apps will just go crazy trying to load stuff it is is not there or make crash some things

basically a mess

[jwt873]

I installed the 64bit -test version on a 120 Gig solid state drive (That I plan to use as my main boot disk when the 64 bit-final comes out).  I'm using an AMD Phenom 4 core computer.

Things sure fly on the SSD...   I normally boot to the command prompt (init3), log in as a user, and then type the startx command to get into X..  It's up and running in four seconds flat!  A conventional SATA hard drive on the same computer takes over 15 seconds.

Out of interest..  Since I'm just messing about with the test version right now... I copied the contents of my working /home partition over to the 64 bit-test /home partition to see what would happen..   It works fine.. Not a hiccup.

I can hardly wait for the 64 bit-final !!!

[menotu]

I can hardly wait for the 64 bit-final !!!

A bit closer.............

Tex just posted:

Going to cut a PCLinuxOS-64bit test 2 iso later today.

and

PCLinuxOS 64 bit packages now at 7,350 including some initial Gnome 3 packages and package updates to keep it current while we build it

[T6]

I installed the 64bit -test version on a 120 Gig solid state drive (That I plan to use as my main boot disk when the 64 bit-final comes out).  I'm using an AMD Phenom 4 core computer.

Things sure fly on the SSD...   I normally boot to the command prompt (init3), log in as a user, and then type the startx command to get into X..  It's up and running in four seconds flat!  A conventional SATA hard drive on the same computer takes over 15 seconds.

why do you want make me cry?!?!

my machine, the best time it can do is 1 minute 20 seconds