On Mon, 3 Sep 2012 14:44:29 +0900 Carsten Haitzler (The Rasterman) <[email protected]> wrote:
> On Mon, 3 Sep 2012 14:32:00 +1000 David Seikel <[email protected]> > said: > > > On Mon, 3 Sep 2012 12:48:47 +0900 Carsten Haitzler (The Rasterman) > > <[email protected]> wrote: > > > > > On Sun, 02 Sep 2012 12:24:21 +0200 Thomas Sachau > > > <[email protected]> said: > > > > > > > Those are simply the previous release versions, i will wait for > > > > the 1.7 addition until the issues with it reported by David > > > > Seikel have been fixed. > > > > > > the issue ONLY affects david. the tarballs build perfectly - > > > unless you have some half-neutered libc that is missing pthread > > > support. you'll be fine. i've tested the tarballs on a pristine > > > chroot and they all build and install correctly and produce > > > correct binaries that work. i repeat - the ONLY person affected > > > is david due to his odd environment. that is why this is a low > > > priority. > > > > Files made it into the tarballs that where deleted as unfit for > > their purpose by the maintainer of those files. The existence of > > the old buggy files overrides the new fixed files. You cannot make > > any guarantees that other problems did not sneak in with those > > broken files. Or even that other broken files did not sneack in > > the same way. THAT's what the issue is, not that I can't build > > without pthreads. Those buggy files have debugging stuff in them, > > they where half way through being debugged. That can't be good for > > a release. > > those files get put there by autogen.sh all the time. i tested the > release tarballs and they all build. you are the only one affected. > that is after a month of alphas, betas and a release. you are the > only one to report any issue. > > > I'm just the one it bit now, you can't say it wont bite others, we > > just don't know. > > > > What you are saying is that coz only one customer found half a > > cockroach in his soup, that the other customers should not worry, > > your soup is good for all. The other half of that cockroach is > > still in someone's soup waiting to be found. In fact you are > > saying that people should ignore any bits of cockroaches they > > happen to find, so long as the soup still tastes good. > > > > My point is not "it breaks for me", which would be a low priority, > > but "it's broken by your method, and only works sometimes by pure > > luck", which should be a high priority. Your method of making this > > release was sloppy. I found half a cockroach. Some of your other > > customers are worried now. Clean the kitchen and make fresh soup. > > > > As I said in my reply to Thomas, if he's not using the release > > tarballs, then there's no issues. SVN is fine, so long as you make > > sure you get a clean SVN. Which is not what you did raster, 1.7.0 > > has one or more cockroaches in it. It's the "or more" part that > > should worry you, not the one that was found. If my project did > > not need to use released tarballs to fit government requirements, > > I'd not care and just use SVN. So, your tarballs are not even fit > > for government work. lol > > that's a problem between you and your employer of having created such > requirements. along with the removal of pthreads. as such this will > no longer be optional in efl so deal with it. we're using more > threads in the internals and there will be no non-threaded path. > > > Or people can use the tarballs, patch around the known half a > > cockroach, and just cross their fingers that there was only half a > > cockroach. > > there is no need to patch around because they work. i TESTED THEM ON > a TOTALLY FRESH SYSTEM (chroot). compiled JUST THE TARBALLS. they > work. the reason they work is the system isn't odd like yours. it > provides all the usual dependencies. > > > It would actually be less of an issue if this release is not > > planned on being the base for the long awaited E17 release. > > Otherwise we could all just go "meh, wait for EFL 1.8.0". You > > should be taking more care with the long awaited release of decades > > of effort. > > > > I know you hate doing releases raster, isn't that why we have a > > release manager? > > it takes hours to spin a new release. i'm not doing it in a hurry - > not for only one person being affected. you had ample opportunity to > report issues in the alpha and beta. you didn't. now you just have to > live with waiting. no one else will be affected but you. You can't say that no one else will be affected by the crufty files issue, you don't know, you can't know. At least one packager thinks that at least one of these issues is a concern. Now he did not state if it was the pthread issue, or the crufty files issue. I'm guessing it's not the pthread issue. If it was just pthreads, I'd not be complaining so much. Please drop the pthread issue, I have. Vincent said that the option to disable threads should not be in there any more. It is in the tarballs, and it is not in SVN. That should be enough to tell you that something is wrong with the tarballs. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
