[haiku] Re: building error

On Thu, Jan 29, 2009 at 12:08 PM, Sean Healy <jalopeura@xxxxxxxxxxx> wrote:
> Urias McCullough wrote:
>
>> First: you should not have to use sudo to build Haiku - it's
>> unnecessary. Once you've used sudo though, much of the files in
>> generated will be owned by root, and you'll get errors when not using
>> sudo.
>
> Actually, the following page on the website instructs people to run jam once
> as a normal user, so that the files built belong to that user, and then a
> second time using sudo, so that you have permission to write to a partition.
>
> http://www.haiku-os.org/documents/dev/installing_haiku_to_a_partition_from_linux

I know this - but it's not required. I'm just trying to enlighten people :)

If you give yourself appropriate read/write permissions to the
/dev/sdx and /dev/sdx# before jam'ing to a partition, all is well. It
saves your generated folder being filled with root-owned files, and
from the whole situation going wrong and writing over something it
shouldn't with your root privileges.

If I had time personally, I'd put some effort into aggregating and
re-writing all the guides out there into something that covers new
enhancements over the last year or two, and covers the various build
environments, along with other important information that people
commonly ask... alas, i'm already swamped so I end up just chiming in
on mailing list or IRC discussions instead.

> Like the user with the problem, this is what I've been doing to build Haiku
> and install it to a partition. Unlike that user, I haven't run into a
> problem. (Although it has been two or three weeks since I've gone through
> the process.) Is this method no longer preferred? If so, how can one go
> about installing Haiku to a partition without using sudo?
>
> By the way, I'm also still using UserBuildConfig rather than a profile, and
> as I mentioned, I haven't had any problems.

UserBuildConfig is where you setup build profiles...it works to use
the image name/dir - but that was a "hack" before the build profiles
gave you direct access to building haiku in various ways without
setting those variables every time.

With build profiles, you can have a single UserBuildConfig that can
build images, partitions, vm images, etc. with simple commands like:

jam -q @disk

or

jam -q @myimage

or even:

jam -q @usbdisk

and it also gives you the ability to update every target on the
disk/image without erasing the contents:

jam -q @disk update-all

these are benefits of using a build profile... I encourage you to look
into the appropriate section of the UserBuildConfig.ReadMe

Other related posts: