gmane.os.apple.fink.devel

Re: New fink release imminent

Alexander Hansen — 2012-05-23T23:31:43

I've put something online at

https://github.com/fink/fink/tree/fink_configure_sets_up_fink_bld

Configure.pm is where things get configured to set.  I check the
validity of prospective UID/GID values here as well as in Services.pm.
If there's a pre-existing fink-bld user, it gets used by default, and
its UID/GID (assumed to be the same) get stored in fink.conf.

Services.pm has similar changes to what Dustin added in his branch, with
a few tweaks.  In this case, the FinkBldUid: field from fink.conf takes
precedence over the current UID/GID of the fink-bld user, so if they
differ the assumption is that the user wanted to change to the fink.conf
value.

Engine.pm actually runs &ensure_fink_bld() thereby setting the fink-bld
user up.  It checks for every fink verb other than "configure".  We may
want only to do that for build operations, perhaps--though it was
convenient just to use "fink index" to test changes to the fink-bld
user. :-)

I'm not sure if everything is compliant with how things need to be set
up when users are managed e.g. via OpenDirectory.

Re: New fink release imminent

Alexander Hansen — 2012-05-22T17:04:30

I don't think fink.conf can handle that.



Actually, what it does right now is:

1) Check whether fink-bld exists on the system, and grab its UID and
GID--via 'id -P fink-bld'.  That avoids worrying about whether the user
happens to have changed fink-bld's configuration by means other than
editing %p/etc/passwd-*, since we're using what is actually in place on
the system.

2) If fink-bld exists and is properly configured (defined as having both
a UID and GID) then the user is given the default option just to use the
extant fink-bld, regardless of whether AutoUid is set.  That way they'll
be using whatever they had set up in the past, unless they specifically
make the change.

For users without fink-bld, the default is to get an ID automatically
from the 600-699 range.

Re: New fink release imminent

Dustin Cartwright — 2012-05-22T08:53:02

On Tue, May 22, 2012 at 6:46 AM, Alexander Hansen
<alexanderk.hansen< at >gmail.com> wrote:

I was just trying to convince you to do less work, but I can see that
I failed. :)


To leave open the possibility of automatic UIDs replacing the current
passwd in the future, would it be better to replace FinkBldUid with
something more extensible? I don't know if the fink.conf parser can
handle something like:

FixedUids: <<
  fink-bld: 266
  postfres: 252
<<

Or maybe better would be just to take the UID and GID from
%p/etc/passwd-fink and %p/etc/passwd-group if AutoUid is false? After
all, this is where people were supposed to customized the added users
in the past.

Dustin


------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: New fink release imminent

Alexander Hansen — 2012-05-22T04:46:38

Sorry, was in a bad mood.

Here's the thought process I was working under:

"fink configure" is a natural place to do anything that has prompts for
the user.  However, it isn't supposed to have side effects, i.e. all
that it currently does is set up the fink.conf file.  So I figured we'd
prompt for user input and do the sanity checking in "fink configure",
saving the results (FinkBldUid for immediate use, and AutoUid,
AutoUidMin, AutoUidMax for the next 'fink configure'), and then actually
write the fink-bld information (if required) elsewhere.

Re: matplotlib-py-1.1.0-3

Merle Reinhart — 2012-05-21T23:30:37

It seems to work ok with my various home-grown tools that do plots.

Merle


On May 21, 2012, at 4:20 PM, Alexander Hansen wrote:



------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: matplotlib-py-1.1.0-3

Alexander Hansen — 2012-05-21T20:20:32

And it seems to work--at least for the test case mentioned in the
tracker entry.

Re: matplotlib-py-1.1.0-3

Alexander Hansen — 2012-05-21T18:39:42


I'm downloading the sources right now.

Re: matplotlib-py-1.1.0-3

Kurt Schwehr — 2012-05-21T18:37:14

I haven't had a chance to look at it, but if a 2nd person can try it, I'd be okay with it.

-kurt

On May 21, 2012, at 11:29 AM, Alexander Hansen wrote:



------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: matplotlib-py-1.1.0-3

Alexander Hansen — 2012-05-21T18:29:27

Any objections to this update?

Re: make testsuite failures

Max Horn — 2012-05-20T17:00:09

Hi Jack,

Am 19.05.2012 um 22:03 schrieb Jack Howarth:

[...]

Those patches used to be absolutely necessary on Mac OS X, as they added support for building Objective C code; omitting them would result in a "make" executable that fails to build lots of OS X specific code. Luckily, in 3.82, upstream finally integrated at least parts of those changes. I am not quite sure why I never picked up 3.82; my guess is that I simply missed the fact that they finally made a new release 4.5 years after 3.81 ;)

Anyway, I just put a 3.82 into CVS. There is a hypothetical chance that it might break a few packages that rely on the other Apple specific features added by that patch -- we'll see. If anybody notices any regressions, let mw know.

As for the remaining two test failures: They are caused by the HFS+ file system which preserves case in filenames, but ignores it for purposes of accessing files. Since those tests are about distinguishing "makefile", "Makefile", etc., it is no wonder they don't work :). It's not a serious issue either, though. I tweaked the test to silence this false failure report.

Cheers,
Max
------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: make testsuite failures

Jack Howarth — 2012-05-19T21:29:02

Max,
   I can also confirm that if the make.patch in the current fink
make 3.81-2 packaging is disabled, these additional 8 testsuite failures
are suppressed. So it appears that this legacy backport from the darwin
make cvs is causing damage to the current make packaging and should either
be fixed or abandoned.
             Jack

------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: make testsuite failures

Jack Howarth — 2012-05-19T20:17:23

Max,
   These last two remaining testsuite failures in unpatched make 3.82 (which
are also present in the current make 3.81-2 package) seem to be longstanding
failures...

http://www.mail-archive.com/bug-make< at >gnu.org/msg05498.html

            Jack

------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

make testsuite failures

Jack Howarth — 2012-05-19T20:03:01

Max,
     We see to have 8 addtional testsuite failures in our make compared to
MacPorts. Adding the missing InfoTest to the current make.info....

InfoTest: TestScript: make check || :

revealed a slew of testsuite failures...

make check || :
Making check in glob
make[1]: Nothing to be done for `check'.
Making check in config
make[1]: Nothing to be done for `check'.
Making check in po
make[1]: Nothing to be done for `check'.
Making check in doc
make[1]: Nothing to be done for `check'.
make  loadavg
gcc -DLOCALEDIR=\"/sw/share/locale\" -DLIBDIR=\"/sw/lib\" -DINCLUDEDIR=\"/sw/include\" -DHAVE_CONFIG_H -I. -I. -I.  -DTEST -mdynamic-no-pic -I/sw/include  -g -O2 -c -o loadavg-getloadavg.o `test -f 'getloadavg.c' || echo './'`getloadavg.c
gcc  -g -O2  -L/sw/lib -o loadavg  loadavg-getloadavg.o  
make  check-local
The system uptime program believes the load average to be:
uptime
cd tests && perl ./run_make_tests.pl -make ../make 
15:42  up  2:55, 5 users, load averages: 0.78 1.04 1.29
The GNU load average checking code thinks:
./loadavg
1-minute: 0.778320  5-minute: 1.037109  15-minute: 1.291016  
------------------------------------------------------------------------------
      Running tests for GNU make on Darwin MacBookPro.local 11.4.0 i386
                                GNU Make 3.81
------------------------------------------------------------------------------

Finding tests...

features/comments ....................................... ok     (1 passed)
features/conditionals ................................... ok     (4 passed)
features/default_names .................................. Error running /sw/src/fink.build/make-3.81-3/make-3.81/tests/../make (expected 0; got 512): /sw/src/fink.build/make-3.81-3/make-3.81/tests/../make

*** Test returned 0
ok     (4 passed)
features/double_colon ................................... ok     (10 passed)
features/echoing ........................................ ok     (4 passed)
features/errors ......................................... ok     (2 passed)
features/escape ......................................... ok     (6 passed)
features/export ......................................... ok     (10 passed)
features/include ........................................ ok     (7 passed)
features/mult_rules ..................................... ok     (2 passed)
features/mult_targets ................................... ok     (2 passed)
features/order_only ..................................... ok     (10 passed)
features/override ....................................... ok     (1 passed)
features/parallelism .................................... ok     (6 passed)
features/patspecific_vars ............................... ok     (7 passed)
features/patternrules ................................... ok     (5 passed)
features/quoting ........................................ ok     (1 passed)
features/recursion ...................................... ok     (2 passed)
features/reinvoke ....................................... ok     (4 passed)
features/se_explicit .................................... ok     (5 passed)
features/se_implicit .................................... ok     (8 passed)
features/se_statpat ..................................... ok     (4 passed)
features/statipattrules ................................. ok     (8 passed)
features/targetvars ..................................... ok     (20 passed)
features/varnesting ..................................... ok     (1 passed)
features/vpath .......................................... ok     (1 passed)
features/vpath2 ......................................... ok     (1 passed)
features/vpathgpath ..................................... ok     (1 passed)
features/vpathplus ...................................... ok     (4 passed)
functions/abspath ....................................... ok     (1 passed)
functions/addprefix ..................................... ok     (1 passed)
functions/addsuffix ..................................... ok     (2 passed)
functions/andor ......................................... ok     (2 passed)
functions/basename ...................................... ok     (1 passed)
functions/call .......................................... ok     (2 passed)
functions/dir ........................................... ok     (1 passed)
functions/error ......................................... ok     (5 passed)
functions/eval .......................................... ok     (9 passed)
functions/filter-out .................................... ok     (1 passed)
functions/findstring .................................... ok     (1 passed)
functions/flavor ........................................ ok     (1 passed)
functions/foreach ....................................... ok     (4 passed)
functions/if ............................................ ok     (1 passed)
functions/join .......................................... ok     (1 passed)
functions/notdir ........................................ ok     (1 passed)
functions/origin ........................................ ok     (1 passed)
functions/realpath ...................................... ok     (2 passed)
functions/shell ......................................... ok     (2 passed)
functions/sort .......................................... ok     (1 passed)
functions/strip ......................................... ok     (2 passed)
functions/substitution .................................. ok     (3 passed)
functions/suffix ........................................ ok     (1 passed)
functions/value ......................................... ok     (1 passed)
functions/warning ....................................... ok     (4 passed)
functions/wildcard ...................................... ok     (3 passed)
functions/word .......................................... ok     (16 passed)
misc/close_stdout ....................................... ok     (0 passed)
misc/general1 ........................................... ok     (1 passed)
misc/general2 ........................................... ok     (1 passed)
misc/general3 ........................................... FAILED (8/10 passed)
misc/general4 ........................................... ok     (6 passed)
options/dash-B .......................................... ok     (7 passed)
options/dash-C .......................................... FAILED (0/2 passed)
options/dash-I .......................................... 
*** Test returned 0
FAILED (0/2 passed)
options/dash-W .......................................... ok     (10 passed)
options/dash-e .......................................... ok     (1 passed)
options/dash-f .......................................... ok     (4 passed)
options/dash-k .......................................... ok     (3 passed)
options/dash-l .......................................... ok     (1 passed)
options/dash-n .......................................... ok     (4 passed)
options/dash-q .......................................... ok     (8 passed)
options/dash-t .......................................... ok     (2 passed)
options/general ......................................... ok     (1 passed)
options/symlinks ........................................ ok     (10 passed)
options/warn-undefined-variables ........................ ok     (2 passed)
targets/DEFAULT ......................................... FAILED (0/1 passed)
targets/FORCE ........................................... ok     (1 passed)
targets/INTERMEDIATE .................................... ok     (8 passed)
targets/PHONY ........................................... ok     (1 passed)
targets/SECONDARY ....................................... ok     (8 passed)
targets/SILENT .......................................... ok     (1 passed)
targets/clean ........................................... ok     (2 passed)
variables/CURDIR ........................................ ok     (1 passed)
variables/DEFAULT_GOAL .................................. ok     (4 passed)
variables/INCLUDE_DIRS .................................. ok     (2 passed)
variables/MAKE .......................................... FAILED (0/1 passed)
variables/MAKECMDGOALS .................................. ok     (3 passed)
variables/MAKEFILES ..................................... ok     (1 passed)
variables/MAKELEVEL ..................................... ok     (1 passed)
variables/MAKE_RESTARTS ................................. FAILED (2/3 passed)
variables/MFILE_LIST .................................... ok     (1 passed)
variables/SHELL ......................................... ok     (5 passed)
variables/automatic ..................................... ok     (5 passed)
variables/flavors ....................................... ok     (10 passed)
variables/negative ...................................... ok     (4 passed)
variables/special ....................................... ok     (1 passed)

10 Tests in 7 Categories Failed (See .diff files in work dir for details) :-(

make[2]: *** [check-regression] Error 1

Updating the package to 3.82 and disabling the make.patch (since MacPorts uses
none for 3.82), I get much improved results of...

make check || :
Making check in glob
make[1]: Nothing to be done for `check'.
Making check in config
make[1]: Nothing to be done for `check'.
Making check in po
make[1]: Nothing to be done for `check'.
Making check in doc
make[1]: Nothing to be done for `check'.
make  loadavg
gcc -DLOCALEDIR=\"/sw/share/locale\" -DLIBDIR=\"/sw/lib\" -DINCLUDEDIR=\"/sw/include\" -DHAVE_CONFIG_H -I.  -DTEST -mdynamic-no-pic -I/sw/include  -g -O2 -c -o loadavg-getloadavg.o `test -f 'getloadavg.c' || echo './'`getloadavg.c
gcc  -g -O2  -L/sw/lib -o loadavg loadavg-getloadavg.o  
make  check-local
The system uptime program believes the load average to be:
uptime
15:45  up  2:58, 5 users, load averages: 0.73 0.88 1.17
The GNU load average checking code thinks:
./loadavg
1-minute: 0.729004  5-minute: 0.878906  15-minute: 1.169434  
cd tests && perl ./run_make_tests.pl -make ../make 
------------------------------------------------------------------------------
      Running tests for GNU make on Darwin MacBookPro.local 11.4.0 i386
                                GNU Make 3.82
------------------------------------------------------------------------------

Finding tests...

features/comments ....................................... ok     (1 passed)
features/conditionals ................................... ok     (4 passed)
features/default_names .................................. Error running /sw/src/fink.build/make-3.82-1/make-3.82/tests/../make (expected 0; got 512): /sw/src/fink.build/make-3.82-1/make-3.82/tests/../make

*** Test returned 0
ok     (4 passed)
features/double_colon ................................... ok     (10 passed)
features/echoing ........................................ ok     (4 passed)
features/errors ......................................... ok     (2 passed)
features/escape ......................................... ok     (6 passed)
features/export ......................................... ok     (12 passed)
features/include ........................................ ok     (10 passed)
features/mult_rules ..................................... ok     (2 passed)
features/mult_targets ................................... ok     (2 passed)
features/order_only ..................................... ok     (10 passed)
features/override ....................................... ok     (4 passed)
features/parallelism .................................... ok     (8 passed)
features/patspecific_vars ............................... ok     (10 passed)
features/patternrules ................................... ok     (10 passed)
features/quoting ........................................ ok     (1 passed)
features/recursion ...................................... ok     (2 passed)
features/reinvoke ....................................... ok     (4 passed)
features/se_explicit .................................... ok     (9 passed)
features/se_implicit .................................... ok     (9 passed)
features/se_statpat ..................................... ok     (4 passed)
features/statipattrules ................................. ok     (8 passed)
features/targetvars ..................................... ok     (23 passed)
features/varnesting ..................................... ok     (1 passed)
features/vpath .......................................... ok     (2 passed)
features/vpath2 ......................................... ok     (1 passed)
features/vpath3 ......................................... ok     (1 passed)
features/vpathgpath ..................................... ok     (1 passed)
features/vpathplus ...................................... ok     (4 passed)
functions/abspath ....................................... ok     (1 passed)
functions/addprefix ..................................... ok     (1 passed)
functions/addsuffix ..................................... ok     (2 passed)
functions/andor ......................................... ok     (2 passed)
functions/basename ...................................... ok     (1 passed)
functions/call .......................................... ok     (2 passed)
functions/dir ........................................... ok     (1 passed)
functions/error ......................................... ok     (5 passed)
functions/eval .......................................... ok     (9 passed)
functions/filter-out .................................... ok     (1 passed)
functions/findstring .................................... ok     (1 passed)
functions/flavor ........................................ ok     (1 passed)
functions/foreach ....................................... ok     (4 passed)
functions/if ............................................ ok     (1 passed)
functions/join .......................................... ok     (1 passed)
functions/notdir ........................................ ok     (1 passed)
functions/origin ........................................ ok     (1 passed)
functions/realpath ...................................... ok     (2 passed)
functions/shell ......................................... ok     (2 passed)
functions/sort .......................................... ok     (1 passed)
functions/strip ......................................... ok     (2 passed)
functions/substitution .................................. ok     (3 passed)
functions/suffix ........................................ ok     (1 passed)
functions/value ......................................... ok     (1 passed)
functions/warning ....................................... ok     (4 passed)
functions/wildcard ...................................... ok     (4 passed)
functions/word .......................................... ok     (16 passed)
misc/close_stdout ....................................... ok     (0 passed)
misc/general1 ........................................... ok     (1 passed)
misc/general2 ........................................... ok     (1 passed)
misc/general3 ........................................... ok     (10 passed)
misc/general4 ........................................... ok     (6 passed)
options/dash-B .......................................... ok     (8 passed)
options/dash-C .......................................... ok     (2 passed)
options/dash-I .......................................... ok     (3 passed)
options/dash-W .......................................... ok     (10 passed)
options/dash-e .......................................... ok     (1 passed)
options/dash-f .......................................... ok     (4 passed)
options/dash-k .......................................... ok     (3 passed)
options/dash-l .......................................... ok     (1 passed)
options/dash-n .......................................... ok     (4 passed)
options/dash-q .......................................... ok     (8 passed)
options/dash-t .......................................... ok     (2 passed)
options/eval ............................................ ok     (2 passed)
options/general ......................................... ok     (1 passed)
options/symlinks ........................................ ok     (10 passed)
options/warn-undefined-variables ........................ ok     (2 passed)
targets/DEFAULT ......................................... ok     (1 passed)
targets/FORCE ........................................... ok     (1 passed)
targets/INTERMEDIATE .................................... ok     (8 passed)
targets/ONESHELL ........................................ ok     (5 passed)
targets/PHONY ........................................... ok     (1 passed)
targets/POSIX ........................................... ok     (2 passed)
targets/SECONDARY ....................................... ok     (12 passed)
targets/SILENT .......................................... ok     (1 passed)
targets/clean ........................................... ok     (2 passed)
variables/CURDIR ........................................ ok     (1 passed)
variables/DEFAULT_GOAL .................................. ok     (5 passed)
variables/INCLUDE_DIRS .................................. ok     (2 passed)
variables/LIBPATTERNS ................................... ok     (2 passed)
variables/MAKE .......................................... ok     (1 passed)
variables/MAKECMDGOALS .................................. ok     (3 passed)
variables/MAKEFILES ..................................... ok     (2 passed)
variables/MAKEFLAGS ..................................... ok     (2 passed)
variables/MAKELEVEL ..................................... ok     (1 passed)
variables/MAKE_RESTARTS ................................. ok     (3 passed)
variables/MFILE_LIST .................................... ok     (1 passed)
variables/SHELL ......................................... ok     (7 passed)
variables/automatic ..................................... ok     (7 passed)
variables/define ........................................ ok     (15 passed)
variables/flavors ....................................... ok     (6 passed)
variables/negative ...................................... ok     (4 passed)
variables/private ....................................... ok     (8 passed)
variables/special ....................................... ok     (2 passed)
variables/undefine ...................................... ok     (4 passed)

2 Tests in 1 Category Failed (See .diff files in work dir for details) :-(

make[2]: *** [check-regression] Error 1
make[1]: *** [check-am] Error 2

We really should address these additional 8 failures in the current fink make
one way or another.
         Jack

------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: New fink release imminent

Alexander Hansen — 2012-05-19T19:35:49

As I've shown in this thread, this is fraught with peril.  A fairly
lengthy sequence of commands is required to provide a working fink-bld
user, so why not put that sequence in fink so that an administrator or
user can just use 'fink configure' and get the right setup with

Even if fink has created

Updating ConfFileCompatVersion forces a prompt after fink is updated
(though it just advises running 'fink configure', has a default choice
of "N", and then moves on.)

I think I'm hesitant only because my

My thought was that _we_ should have an interface to control how _our_
user gets set up, and that the user should be involved, as David
mentioned (we also discussed this on IRC).

I'd thought that it would be nice to have that information in fink.conf
so that we could maintain some internal consistency on people's systems
when we're generating IDs dynamically.

I'm done.  We can come back to this once Mountain Lion is out.

Re: New fink release imminent

Dustin Cartwright — 2012-05-19T12:59:21

On Fri, May 18, 2012 at 10:55 PM, Alexander Hansen <
alexanderk.hansen< at >gmail.com> wrote:

As you like, but this seems excessively complicated to me for no real gain.
What's the difference between:

1. Setting AutoUidBase to n
2. Setting AutoUidBase and AutoUidMax both to n
3. Setting AutoUid to false and setting FinkBldUid to n

As I see it, these are basically telling fink:

1. Create fink-bld with UID n, unless it's already used, in which case take
the next available UID.
2. Create fink-bld with UID n, unless it's already used, in which case fail
and don't create fink-bld at all.
3. Create fink-bld with UID n, even if it's in use because I don't care
whether or not I have to users with the same UID.

1 seems the most useful to me. Maybe some people would prefer the extra
control that comes with 2. But why would anyone prefer 3 over 1 or 2? It
seems like a good principle that fink should never create a user with a UID
that already exists. If you believe that, then the only configuration
options which make sense are those giving fink a range of UIDs to use.

And for people who want to control which UIDs fink uses, there are options,
even without extra configuration parameters. They can use AutoUidBase to
restrict the UIDs to a specific range. They can create the fink-bld user
themselves with "dscl". Even if fink has created fink-bld, they can change
its UID using "dscl". If they're on a network, they can create fink-bld on
the central directory and then it will be on all the other computers with
the same UID.

When fink is invoked for a build, it will check whether the fink-bld

As I said, if someone wants to change fink-bld's UID, they can type:

sudo dscl . /Users/fink-bld UniqueID <new id>

This is not really any more complicated than setting a line in fink.conf.
On the other hand, putting some code into fink which will modify the user
database under circumstances where it will only rarely get invoked seems
like a dangerous idea to me.

My opinion is that it would be best to just have two new configuration
settings: AutoUidMin (rather than AutoUidBase) and AutoUidMax. Also, I've
come around to the idea that there should be a prompt for AutoUidMin during
configure (and thus during bootstrap). Probably there should also be a
prompt the first time the user upgrades to a version of fink which uses
this option. I think I'm hesitant only because my annoyance at the passwd
package for requiring user interaction during the build process makes me
not want to add prompts where they don't normally exist.

Dustin
------------------------------------------------------------------------------
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/_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: New fink release imminent

Alexander Hansen — 2012-05-18T20:55:07

My thought is to borrow from what you've done, but do like David and
Merle suggested and store the following in fink.conf:

AutoUid: boolean

AutoUidBase: integer, default 600

AutoUidMax: integer, default 699

FinkBldUid: the UID

FinkBldGid: the GID


AutoUid, FinkBldUid, and FinkBldGid would get set via "fink configure".
 Networked folks would set AutoUid: false via a prompt, and FinkBldUid
and FinkBldGid would either be autogenerated, use an existing value
(left over from passwd-fink-bld) or have values set explicitly,
depending on what the user wants.  (AutoUidBase and AutoUidMax wouldn't
be set by prompts, but would be changed via manually editing fink.conf).

When fink is invoked for a build, it will check whether the fink-bld
user exists.  If not, it will be created using these parameters from
fink.conf.  If the UID and GID from fink.conf are different than those
in Directory Services, fink-bld will be updated to match fink.conf.

Re: New fink release imminent

Dustin Cartwright — 2012-05-17T21:12:16

On Thu, May 17, 2012 at 9:35 PM, Alexander Hansen <
alexanderk.hansen< at >gmail.com> wrote:


Good to hear. I'd recommend rebasing your patch to da556100d53. The last
commit to dustinac/add-fink-bld added a call to dsmemberutil, which was an
apparently wrong attempt to resolve the caching issue. Leaving it in would
be very confusing to anyone who later tries to understand the code.

So, what about networked users?

Dustin
------------------------------------------------------------------------------
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/_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: New fink release imminent

Alexander Hansen — 2012-05-17T19:35:28

Success!

What passwd-fink-bld does, and which wasn't being done by fink either in
my branch or Dustin's, is to run

dscl . -delete /Users/fink-bld AuthenticationAuthority

when generating the fink-bld user.  By doing this, I get the proper results:

10.7

$ id fink-bld
uid=600(fink-bld) gid=600(fink-bld)
groups=600(fink-bld),402(com.apple.sharepoint.group.1),403(com.apple.sharepoint.group.2),12(everyone),61(localaccounts)


10.6

$id fink-bld
uid=600(fink-bld) gid=600(fink-bld)
groups=600(fink-bld),101(com.apple.sharepoint.group.1),61(localaccounts),12(everyone),102(com.apple.sharepoint.group.2)

10.5

$ id fink-bld
uid=600(fink-bld) gid=600(fink-bld) groups=600(fink-bld)

Re: New fink release imminent

Alexander Hansen — 2012-05-17T17:44:41

Woops, I was wrong.  I get the same thing on 10.7 from my
"fink-creates-fink-bld" branch when I create fink-bld in fink's
postinstall.

------------------------------------------------------------------------------
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/
_______________________________________________
Fink-devel mailing list
Fink-devel< at >lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-users] fink update-all fails on 10.7.4

Alexander Hansen — 2012-05-17T17:02:43

I went ahead and pushed the xcode_app branch upstream:

https://github.com/fink/fink/tree/xcode_app

I won't merge it into master just yet.

Re: new p7zip version

Alexander Hansen — 2012-05-17T16:57:05

Thanks!  I'll go ahead and list myself as maintainer.