Re: --build-as-nobody by default.

Am 12.04.2012 um 01:01 schrieb Alexander Hansen:

> It seems like Daniel J.'s '--build-as-nobody by default' branch is ripe 
> for inclusion in git master:  it's got the .info file spec to turn the 
> behavior off:  BuildAsNobody: false and a command line option to turn it 
> off: " --no-build-as-nobody".
> 
> 3 questions:
> 
> 1)  Any objections to bringing this in to the main repository?

It seems that this has been merged already shortly after this question was asked. While I don't really mind that, I am somewhat concerned about this change, see the end of this email.

> 2)  Assuming not, should we just do this via having danielj file a 
> github pull request to merge his branch into master?

Yes. In fact, in the future I would recommend directly including a link to a relevant pull request, that makes it a tad easier to conveniently look at it.

>  He has kept them in sync.

That's actually a bad thing in general :-/. A typical "good" git branch strategy is to *not* merge upstream into your branches unless you really have to. This helps keep a sane history. As it is, out of 12 commits, 9 are useless merge commits, which seem to serve no real purpose.


> 3)  Since this changes a default behavior in the fink tool and requires 
> new .info file fields, should we move on from 0.32.x to 0.33 at that point?

Actually, before we decide that, shouldn't we first talk about a potential transition strategy for this? If we just drop this in, it would break lots of packages right away. This might upset a lot of users and some maintainers. So, it would be nice to mark as many of the packages that require "BuildAsNobody: false" as such. But if authors do this now, this will cause their packages to fail validation, as the current fink release does not support BuildAsNobody. I.e. we have a chicken and egg problem.

How about this strategy instead: First we turn off BuildAsNobody globally again by default. Then we make a release with the new BuildAsNobody field and command line option in it. *Then* we email to -devel and ask all authors to check their packages (and how) and add BuildAsNobody as needed. Meanwhile, we update all base packages as necessary. Finally, after a certain grace period (I'd suggest a month or two at least), we can turn off BuildAsNobody globally. Some packages will still break, but at least this way we give maintainers a fair chance to fix their act. As opposed to forcing them to fix their packages IMMEDIATELY after the release or else potentially getting tons of user complaints for something that might not even be avoidable from their side. In addition, this approach might redu
 ce the pain for our users a bit, too... ;).

Cheers,
Max
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
fink-core mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core