Thanks for your comment.
"--force" works to me now.
And I will look into jhbuild for further development.
Could you give me a quick guide or web page about how to work with jhbuild.

Thanks in advance
-Bob

----- Original Message ----- From: "Roger WANG" <[email protected]>
To: <[email protected]>; <[email protected]>
Sent: Friday, August 28, 2009 11:09 AM
Subject: Re: [Moblin Dev] How to avoid package conflict when updating


On Fri, 2009-08-28 at 10:56 +0800 Lynch, Rusty wrote:
On Thu, 2009-08-27 at 18:45 -0700, Roger WANG wrote:
> On Fri, 2009-08-28 at 09:36 +0800 bob wrote:
> > I tried "-U" option and conflict still exists. I'm doing development > > under a > > NB with Moblin2, and Mutter-moblin is a runtime GUI function. Maybe > > that's
> > the reason to conflict.
>
> You might want to try the '--force' option with rpm.

I would not recommend using --force unless you really know what your
doing.  Blindly force installing random packages is a quick way to end
up with a completely hosed rpm database.

That would be fine in bob's case.


>
> For a regular development cycle, you may also want to keep up with git
> tip, make some hack, then build and have a try. Setting a work
> environment with 'jhbuild' gives you a shorter cycle -- you don't have
> to build & install rpm every time you try.

Using jhbuild is fine and all, but there shouldn't be any conflicts
introduce by building a package locally and then manually installing
it.

jhbuild handles that pretty well -- completly indepent source and
install locations.


That is.. unless you picked up a non-moblin source rpm, and were unlucky
enough to for this new package to try and install files that are already
owned by some other package.

I recommend getting the source from git for developers, for better
integrated to the development process (keeping up with upstream,
working on branches, generating / sending patches, etc..)

Roger
_______________________________________________
Moblin dev Mailing List
[email protected]

To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org once logged in.

For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists

_______________________________________________
Moblin dev Mailing List
[email protected]

To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org 
once logged in.

For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists

Reply via email to