On 7/18/2012 5:23 AM, Linda Walsh wrote:
Anders Johansson wrote:
On Tuesday 17 July 2012 14:38:44 Linda Walsh wrote:
Juergen Weigert wrote:
On Jul 17, 12 11:37:57 -0300, Claudio Freire wrote:
If a package builds differently in different environments, it's bad for stability to actually build it in different environments. You want to be sure you'll build it the same way each time, so you know you're not introducing bugs by simply rebuilding. For asserting a particular environment, we need to do two thing: a) make sure everything is there that should be there. b) make sure nothing is there that should not.
BuildConflicts appears to be the tool to keep packages out. While BuildRequires is quite practical for a), BuildConflicts appears to be not so helpful for b). It would require a patient maintainer to find all possible conflicts.
Certainly, most people would consider it a bug if the package rpms you were building, were installed after the build, and the build was repeated -- and then failed.
What you are saying makes exactly no sense on any level I know -- but it is the case.
, but just FYI: samba was installed on my machine when I (successfully) rebuilt it
Anders Make sure you install the "-devel" packages, libldb-devel libtevent-devel libtdb-devel libtalloc-devel libwbclient-devel libsmbsharemodes-devel libnetapi-devel libsmbclient-devel samba-devel
Makes sense to install the devel packages if you are going to compile and devel samba, right? In fact make sure you install all the -devel packages for the packages you install... that way you'll be prepared to compile anything...
Just installing the user-level packages isn't what someone wanting to build everything would normally do...
Oh, and tell me about the manpages for ldb... how'd those turn out for you?
tdbrestore? talloc? Libraries are there, but did your manpages install?
Lemme know how that works out for you...
So far, all of your problems have been the result of you just not knowing how to use linux. This is not anyone else's fault. Please become conversant in the system you are trying to use before trying to claim that there is any problem with the system you are trying to use. Ask all the questions you want when you run into things that don't work as expected for you, but understand that at least for now, all problems are the result of lacks in your education, not lacks in the system. All unmet expectations are the result of faulty expectations, not faulty system. It's not perfect indeed, and there may indeed possibly be holes. But you are not even close to being able to help find and close them yet. You have not found a hole everyone else missed. Go ahead and tell me you've been using unix for years, it doesn't change the fact that you've so far been just plain wrong. We can all build all this same software using only free tools and not requiring any external services, accounts, tools, closed software. What IS required is effort and knowledge on your part. Absolutely there is a bar you must attain. No one is obligated to make it all work by magic for you. No one is even obligated to prove to you personally that the necessary tools, source files and even documentation are all available and that they work. Those things _are_ all there, and can be demonstrated by anyone at any time. Rather it's the other way around. If YOU want to claim that the necessary files and tools are not available, it falls on YOU to prove it. This you have not done, even though you think you have. You have only proved that you don't know how to figure things out and that if you try some random thing without any effort or understanding, it doesn't work. Well Congratulations, you discovered that technology doesn't work by itself by magic, but must actually be understood and *made* to work. If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org