muttprint port hangs (muttprint/perl)

2011-12-15 Thread Daniel P. Wright
Hello,

I am having some problems running the print/muttprint port.  If I pass
in a simple text file (some mail headers and a single line of text
reading Test), it hangs indefinitely.  If I send a SIGINT I get the
following output:

  ^CCaught a SIGINT at ./muttprint line 1962

Line 1962 looks fairly innocuous:

  my @text = $fh;

Where $fh is a file handle pointing to the simple text file mentioned
above and passed into the function.

My knowledge of perl is not great, but my understanding is that the
$fh syntax is similar to a readline?  I tried changing this to call
the readline function explicitly, to no effect.

On a hunch I thought my locale might be causing problems, as it is set
to ja_JP.UTF-8, and I don't believe muttprint officially supports that
locale.  I tried setting it to en_US, but it still hangs.

I am not sure whether this is a problem with muttprint itself, or
a quirk of the FreeBSD perl port (--version reports 5.12.4), or
something peculiar to my setup.

For what it's worth, I have previously had muttprint working on Ubuntu
installed from the tar.gz file on the muttprint website.  Diffing the
two versions reveals only superficial changes (penguin replaced with
Beastie, etc).

Apologies if I have the wrong list for this sort of thing.  I took a
look on freshports and there appears to be no active maintainer.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


lang/gcc on freebsd 10

2011-12-15 Thread Andriy Gapon

lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22
installed during its configure step with the errors like the following in
config.log:

configure:2978: checking for C compiler default output file name
configure:3000:  /usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/xgcc
-B/usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/
-B/usr/local/x86_64-portbld-freebsd10.0/bin/
-B/usr/local/x86_64-portbld-freebsd10.0/bin/
-B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem
/usr/local/x86_64-portbld-freebsd10.0/include -isystem
/usr/local/x86_64-portbld-freebsd10.0/sys-include-g -O2 -gtoggle
-static-libstdc++ -static-libgcc  conftest.c  5
xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found

It seems that the error occurs because the preceding steps create
liblto_plugin.so.0.0 file, but no liblto_plugin.so link to it.  Not sure why is
that though.  Maybe something about platform misdetection.

-- 
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: lang/gcc on freebsd 10

2011-12-15 Thread Andriy Gapon
on 15/12/2011 12:59 Andriy Gapon said the following:
 
 lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22
 installed during its configure step with the errors like the following in
 config.log:
 
 configure:2978: checking for C compiler default output file name
 configure:3000:  /usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/xgcc
 -B/usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/
 -B/usr/local/x86_64-portbld-freebsd10.0/bin/
 -B/usr/local/x86_64-portbld-freebsd10.0/bin/
 -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem
 /usr/local/x86_64-portbld-freebsd10.0/include -isystem
 /usr/local/x86_64-portbld-freebsd10.0/sys-include-g -O2 -gtoggle
 -static-libstdc++ -static-libgcc  conftest.c  5
 xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found
 
 It seems that the error occurs because the preceding steps create
 liblto_plugin.so.0.0 file, but no liblto_plugin.so link to it.  Not sure why 
 is
 that though.  Maybe something about platform misdetection.
 

Yeah, lto-plugin/configure:

freebsd* | dragonfly*)
  # DragonFly does not have aout.  When/if they implement a new
  # versioning mechanism, adjust this.
  if test -x /usr/bin/objformat; then
objformat=`/usr/bin/objformat`
  else
case $host_os in
freebsd[123]*) objformat=aout ;;
*) objformat=elf ;;
esac
  fi

freebsd[123]* is it.
Other configure scripts have this thing too.

-- 
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: lang/gcc on freebsd 10

2011-12-15 Thread Kostik Belousov
On Thu, Dec 15, 2011 at 12:59:02PM +0200, Andriy Gapon wrote:
 
 lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22
 installed during its configure step with the errors like the following in
 config.log:
 
 configure:2978: checking for C compiler default output file name
 configure:3000:  /usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/xgcc
 -B/usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/
 -B/usr/local/x86_64-portbld-freebsd10.0/bin/
 -B/usr/local/x86_64-portbld-freebsd10.0/bin/
 -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem
 /usr/local/x86_64-portbld-freebsd10.0/include -isystem
 /usr/local/x86_64-portbld-freebsd10.0/sys-include-g -O2 -gtoggle
 -static-libstdc++ -static-libgcc  conftest.c  5
 xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found
 
 It seems that the error occurs because the preceding steps create
 liblto_plugin.so.0.0 file, but no liblto_plugin.so link to it.  Not sure why 
 is
 that though.  Maybe something about platform misdetection.
.0.0 is almost sure indication of another case of FreeBSD-10 bug, i.e.
freebsd1* glob that used to detect a.out shared libraries.


pgpBSdrvbx6tS.pgp
Description: PGP signature


Re: Building ports with gcc46

2011-12-15 Thread Andrew W. Nosenko
On Thu, Dec 15, 2011 at 02:05, b. f. bf1...@googlemail.com wrote:
 If you are interested in applying them to a single port, use a test on 
 .CURDIR,
 or, better yet, add the statement to any of the optional Makefiles that are
 automatically included by bsd.port.mk and were intended for that purpose --
 ${MASTERDIR}/Makefile.local, for example.

Unfortunatelly, the Makefile.local included too late for have any
positive/intended effect (e.g. define port-specific WITH/WITHOUT knob,
modify CONFIGURE_ARGS,...) in many cases/ports.  Therefore, advise to
use Makefile.local is unreliable.  And we left in situation, where
make.conf is the only one reasonable working solution :-(

But yes, it should be properly conditionalized by .if/.endif

-- 
Andrew W. Nosenko andrew.w.nose...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: lang/gcc on freebsd 10

2011-12-15 Thread Gerald Pfeifer
On Thu, 15 Dec 2011, Andriy Gapon wrote:
 lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22
 installed during its configure step with the errors like the following in
 config.log:

Yes, I am aware of it.  lang/gcc is the slowly moving, conservative
option, lang/gcc46 being the fast, aggressive one.  In consequence,
lang/gcc46 has already been fixed with regard to FreeBSD 10, whereas
this likely will take another month or so for lang/gcc when the next
upstream release hapens.

(Had I better network connectivity right now, I might try the backport, 
but really the use case for lang/gcc at this point is not users of
FreeBSD 10.  That's going to change with the changes to Mk/bsd.gcc.mk
that we discussed on this list the last couple of days, and that will
not happen before it builds on FreeBSD 10.)

Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: lang/gcc on freebsd 10

2011-12-15 Thread Andriy Gapon
on 15/12/2011 16:42 Gerald Pfeifer said the following:
 On Thu, 15 Dec 2011, Andriy Gapon wrote:
 lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22
 installed during its configure step with the errors like the following in
 config.log:
 
 Yes, I am aware of it.  lang/gcc is the slowly moving, conservative
 option, lang/gcc46 being the fast, aggressive one.  In consequence,
 lang/gcc46 has already been fixed with regard to FreeBSD 10, whereas
 this likely will take another month or so for lang/gcc when the next
 upstream release hapens.
 
 (Had I better network connectivity right now, I might try the backport, 
 but really the use case for lang/gcc at this point is not users of
 FreeBSD 10.  That's going to change with the changes to Mk/bsd.gcc.mk
 that we discussed on this list the last couple of days, and that will
 not happen before it builds on FreeBSD 10.)

Thank you for the information.

-- 
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Global and User package database

2011-12-15 Thread Mehmet Erol Sanliturk
Dear All ,


In the new PkgNG :

https://github.com/pkgng/pkgng/blob/master/pkg/add.c


the following statement is written :

if (geteuid() != 0) {
warnx(adding packages can only be done as root);
return (EX_NOPERM);
}


Instead of the above statement , is it possible to use a statement
as follows ( which it may be defined as a function to be called from all
the related
functions / programs ) :



if (geteuid() == 0) {

 package_db_path = ... global path name ... , etc. ;


 PKGDB_PLACE  =  PKGDB_DEFAULT ...  etc.


} else
 {


 package_db_path = ... local path name , ie.
 in $HOME about user path name ... , etc. ;

  PKGDB_PLACE  =  PKGDB_USER ... etc.

  }

if (pkgdb_open(db, PKGDB_PLACE) != EPKG_OK) {
 return (EX_IOERR);
}


( Replace PKGDB_PLACE by a suitable name ... )


In that way , it will be possible to install packages into user home
directory ,
instead of global package directory .

For security concerns , user-installed packages will not be usable globally
, or
convenient only for the user .



Thank you very much .

Mehmet Erol Sanliturk
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Fwd: Lousy timekeeping in VirtualBox 4.0.14

2011-12-15 Thread Larry Rosenman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Moving to -ports, as maybe -virtualization is the wrong list?



-  Original Message 
Subject: Lousy timekeeping in VirtualBox 4.0.14
Date: Wed, 14 Dec 2011 14:04:31 -0600
From: Larry Rosenman l...@lerctr.org
Organization: LERCTR Consulting
To: freebsd-virtualizat...@freebsd.org

- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've set up VirtualBox 4.0.14 on my FreeBSD 10.0-CURRENT (r228498)
box, and have a FreeBSD 10.0-CURRENT VM running underneath it.

While the VM is running, it doesn't keep time worth a flip.

This is even with the VirtualBox-Additions in it.

1) is this expected/known?
2) What can we do to fix it?

What diagnostics do you need?

I *CAN* provide ssh access to both the host and the guest.


- - --
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: l...@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
- -BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJO6QFPAAoJENC8dtAvA1zm3AEH/3b4G0/MUVKCICUz+Yzjobww
wdH53JJCxI0IIXxQuxkisbfjQyhJhrvzCOsWEB0gg2WPZ1cnycoBTTebX6+ALaGW
D5yclMj46Nt02W6zhVUqnPc8drVnUCscSgN1Ow+aGD7fCK1xTTfeGNLM9afmAXRs
tUNZWmg1R4eEAvOi/tnA82p+VVfj0lxxpoEaEhJgy0oougFphN5jpDeWtbSGzJhB
sCeaxUpjOjiM4+B6HTRGnS8A2lqRuPPlS5JOR5Dfae98o/0Dl1Yl95C/O9iItFca
yFxwA3OhEkGw4IMFSbabz3HCPwX75Fp90zcZuoNy2ZDLw53uMJ1oJeoxJ7RqPhE=
=9hON
- -END PGP SIGNATURE-
___
freebsd-virtualizat...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
freebsd-virtualization-unsubscr...@freebsd.org

- -- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: l...@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJO6lRhAAoJENC8dtAvA1zm524H/0Ypp9YfBFeef12uApa17uqX
j0EEuOc4B1Eie66ib1qAGGRW0AfmJu00daa7dl8oT5bMQq1MkpiU8C6WVBpPHjjR
f+ZPA1vvqDCAoLPStgbyMgMxDpxl0bw/2xT7BOk/wAPHfbRzjPS5dthLSJ9xi0vA
s6ki5ZfJkzsgoIzXBw3iQmLXTltjRHwAHQ5rIO+JwswCV5jkQlKMATd/NCIS30Eb
iQQc93HzCcRpXsb8xEqrgwCtozer87d3+O6RhRq8WGOoscTm3LgY+VgoxexwIZ0r
4U06HvHtONxVY4at2xvJpm+Mek2zdpZgNoE5IsKGqm0gJlaQREE0WFbn5KWqBQs=
=R5ha
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Building ports with gcc46

2011-12-15 Thread Greg Larkin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/15/11 9:37 AM, b. f. wrote:
 On 12/15/11, Andrew W. Nosenko andrew.w.nose...@gmail.com wrote:
 On Thu, Dec 15, 2011 at 02:05, b. f. bf1...@googlemail.com wrote:
 If you are interested in applying them to a single port, use a test on
 .CURDIR,
 or, better yet, add the statement to any of the optional Makefiles that
 are
 automatically included by bsd.port.mk and were intended for that purpose
 --
 ${MASTERDIR}/Makefile.local, for example.

 Unfortunatelly, the Makefile.local included too late for have any
 positive/intended effect (e.g. define port-specific WITH/WITHOUT knob,
 modify CONFIGURE_ARGS,...) in many cases/ports.  Therefore, advise to
 use Makefile.local is unreliable.  And we left in situation, where
 make.conf is the only one reasonable working solution :-(
 
 Certainly Makefile.local is not included as early as make.conf, and so
 may not be used for every purpose for which make.conf may be used.
 But with regard to the topic of this thread, Makefile.local  is
 included before options-handling, and the test for inclusion of
 bsd.gcc.mk.  Why did you think otherwise?  Using Makefile.local is
 generally safer because of its narrower scope, and because it cannot
 be included multiple times if make(1) is invoked recursively, unlike
 make.conf.
 
 b.

Hi everyone,

Thank you for the correction to placement of the USE_GCC directive.
Clearly, I went for the hammer solution a little too quickly!

Cheers,
Greg
- -- 
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/  - Follow you, follow me
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7qXIYACgkQ0sRouByUApAruACfbbesKuJBXybzJamMxFwm18tE
cfkAnA2VsTCB+VfChcWd3mHf+/mgibf8
=aKXZ
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Global and User package database

2011-12-15 Thread Baptiste Daroussin
On Thu, Dec 15, 2011 at 02:10:57PM -0500, Mehmet Erol Sanliturk wrote:
 Dear All ,
 
 
 In the new PkgNG :
 
 https://github.com/pkgng/pkgng/blob/master/pkg/add.c
 
 
 the following statement is written :
 
 if (geteuid() != 0) {
 warnx(adding packages can only be done as root);
 return (EX_NOPERM);
 }
 
 
 Instead of the above statement , is it possible to use a statement
 as follows ( which it may be defined as a function to be called from all
 the related
 functions / programs ) :
 
 
 
 if (geteuid() == 0) {
 
  package_db_path = ... global path name ... , etc. ;
 
 
  PKGDB_PLACE  =  PKGDB_DEFAULT ...  etc.
 
 
 } else
  {
 
 
  package_db_path = ... local path name , ie.
  in $HOME about user path name ... , etc. ;
 
   PKGDB_PLACE  =  PKGDB_USER ... etc.
 
   }
 
 if (pkgdb_open(db, PKGDB_PLACE) != EPKG_OK) {
  return (EX_IOERR);
 }
 
 
 ( Replace PKGDB_PLACE by a suitable name ... )
 
 
 In that way , it will be possible to install packages into user home
 directory ,
 instead of global package directory .
 
 For security concerns , user-installed packages will not be usable globally
 , or
 convenient only for the user .
 
 
 
 Thank you very much .
 
 Mehmet Erol Sanliturk

This is an interesting idea, but it deserves more thinking about it, because it
could have more impacts.

Could you please fill an issue on the github so that we won't forget the idea
and will be able to discuss it.

I don't think we will propose that feature for 1.0 but maybe it could be
discussed for 2.0 :)

regards,
Bapt


pgpuuX6rf9FAs.pgp
Description: PGP signature


Re: Building ports with gcc46

2011-12-15 Thread Greg Larkin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/14/11 9:35 PM, Ali Mashtizadeh wrote:
 That gives the same error as the one of my previous attempts. Any help
 with this would be great.
 
 libtool: link: g++46 -D_THREAD_SAFE -pthread -Wall -Wwrite-strings
 -Woverloaded-virtual -Wno-sign-compare -O2 -pipe
 -Wl,-rpath=/usr/local/lib/gcc46 -fno-strict-aliasing -D_THREAD_SAFE
 -pthread -Wl,-rpath=/usr/local/lib/gcc46 -o .libs/protoc main.o
 ./.libs/libprotobuf.so ./.libs/libprotoc.so
 /usr/ports/devel/protobuf/work/protobuf-2.4.1/src/.libs/libprotobuf.so
 -lz -pthread -Wl,-rpath -Wl,/usr/local/lib/usr/local/bin/ld:
 .libs/protoc: hidden symbol `__dso_handle' in
 /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/crtbegin.o is
 referenced by DSO/usr/local/bin/ld: final link failed: Bad
 valuecollect2: ld returned 1 exit statusgmake[2]: *** [protoc] Error
 1gmake[2]: Leaving directory
 `/usr/ports/devel/protobuf/work/protobuf-2.4.1/src'gmake[1]: ***
 [all-recursive] Error 1gmake[1]: Leaving directory
 `/usr/ports/devel/protobuf/work/protobuf-2.4.1'gmake: *** [all] Error
 2*** Error code 1
 Stop in /usr/ports/devel/protobuf.

Hi Ali,

I was able to successfully link protoc by hand by building main.o with
- -fPIC and making sure that the -shared flag was used to compile all
source files.

Unfortunately, the executable core dumps immediately, and there's no
useful stack frame in gdb.  I'll have to defer to GCC experts at this point.

Best of luck,
Greg
- -- 
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/  - Follow you, follow me
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7qYW4ACgkQ0sRouByUApBCYACfUZCbqge2dP/PcQLq7xMyL83b
g/AAoK1ZikafAsPfdvs6eBoSk4vTMS7R
=eOnI
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: A maintainers question: how to create a user?

2011-12-15 Thread Aryeh Friedman
On Thu, Dec 15, 2011 at 7:16 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:

 See subject for the main question... the details: I am the maintainer of
 devel/aegis and the final installation step typically (linux RPM's for
 example) is to create a user to hold the baselines (in svn/cvs/csup speak
 the project's repo) of the varioous projects managed by aegis... customerly
 this is MUST be a non-logginable (you MUST [requirements document meaning
 of upper case MUST/SHOULD/MAY {NOT}) but allow for su from either root or
 via sudo a member of wheel)... it is a standard account in all other
 respects for example I typically set it to tcsh but the port might want to
 make that an make time option... what is the best way of setting this all
 up (both the no options and the options based versions)


for example:

# grep aegis /etc/passwd
aegis:*:1002:1002:Aegis Baselines:/home/aegis:/bin/tcsh
# grep aegis /etc/group
wheel:*:0:root,aryeh,aegis
aegis:*:1002:
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


A maintainers question: how to create a user?

2011-12-15 Thread Aryeh Friedman
See subject for the main question... the details: I am the maintainer of
devel/aegis and the final installation step typically (linux RPM's for
example) is to create a user to hold the baselines (in svn/cvs/csup speak
the project's repo) of the varioous projects managed by aegis... customerly
this is MUST be a non-logginable (you MUST [requirements document meaning
of upper case MUST/SHOULD/MAY {NOT}) but allow for su from either root or
via sudo a member of wheel)... it is a standard account in all other
respects for example I typically set it to tcsh but the port might want to
make that an make time option... what is the best way of setting this all
up (both the no options and the options based versions)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Global and User package database

2011-12-15 Thread Mehmet Erol Sanliturk
On Thu, Dec 15, 2011 at 4:06 PM, Baptiste Daroussin b...@freebsd.orgwrote:

 On Thu, Dec 15, 2011 at 02:10:57PM -0500, Mehmet Erol Sanliturk wrote:
  Dear All ,
 
 
  In the new PkgNG :
 
  https://github.com/pkgng/pkgng/blob/master/pkg/add.c
 
 
  the following statement is written :
 
  if (geteuid() != 0) {
  warnx(adding packages can only be done as root);
  return (EX_NOPERM);
  }
 
 
  Instead of the above statement , is it possible to use a statement
  as follows ( which it may be defined as a function to be called from all
  the related
  functions / programs ) :
 
 
 
  if (geteuid() == 0) {
 
   package_db_path = ... global path name ... , etc. ;
 
 
   PKGDB_PLACE  =  PKGDB_DEFAULT ...  etc.
 
 
  } else
   {
 
 
   package_db_path = ... local path name , ie.
   in $HOME about user path name ... , etc. ;
 
PKGDB_PLACE  =  PKGDB_USER ... etc.
 
}
 
  if (pkgdb_open(db, PKGDB_PLACE) != EPKG_OK) {
   return (EX_IOERR);
  }
 
 
  ( Replace PKGDB_PLACE by a suitable name ... )
 
 
  In that way , it will be possible to install packages into user home
  directory ,
  instead of global package directory .
 
  For security concerns , user-installed packages will not be usable
 globally
  , or
  convenient only for the user .
 
 
 
  Thank you very much .
 
  Mehmet Erol Sanliturk

 This is an interesting idea, but it deserves more thinking about it,
 because it
 could have more impacts.

 Could you please fill an issue on the github so that we won't forget the
 idea
 and will be able to discuss it.

 I don't think we will propose that feature for 1.0 but maybe it could be
 discussed for 2.0 :)

 regards,
 Bapt




The issue has been created .

During program writing , design and implementation at the beginning is much
more easier than modifications
performed after a completed design and implementation .


Thank you very much .

Mehmet Erol Sanliturk
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Global and User package database

2011-12-15 Thread Baptiste Daroussin
On Thu, Dec 15, 2011 at 10:13:19PM -0500, Mehmet Erol Sanliturk wrote:
 On Thu, Dec 15, 2011 at 4:06 PM, Baptiste Daroussin b...@freebsd.orgwrote:
 
  On Thu, Dec 15, 2011 at 02:10:57PM -0500, Mehmet Erol Sanliturk wrote:
   Dear All ,
  
  
   In the new PkgNG :
  
   https://github.com/pkgng/pkgng/blob/master/pkg/add.c
  
  
   the following statement is written :
  
   if (geteuid() != 0) {
   warnx(adding packages can only be done as root);
   return (EX_NOPERM);
   }
  
  
   Instead of the above statement , is it possible to use a statement
   as follows ( which it may be defined as a function to be called from all
   the related
   functions / programs ) :
  
  
  
   if (geteuid() == 0) {
  
package_db_path = ... global path name ... , etc. ;
  
  
PKGDB_PLACE  =  PKGDB_DEFAULT ...  etc.
  
  
   } else
{
  
  
package_db_path = ... local path name , ie.
in $HOME about user path name ... , etc. ;
  
 PKGDB_PLACE  =  PKGDB_USER ... etc.
  
 }
  
   if (pkgdb_open(db, PKGDB_PLACE) != EPKG_OK) {
return (EX_IOERR);
   }
  
  
   ( Replace PKGDB_PLACE by a suitable name ... )
  
  
   In that way , it will be possible to install packages into user home
   directory ,
   instead of global package directory .
  
   For security concerns , user-installed packages will not be usable
  globally
   , or
   convenient only for the user .
  
  
  
   Thank you very much .
  
   Mehmet Erol Sanliturk
 
  This is an interesting idea, but it deserves more thinking about it,
  because it
  could have more impacts.
 
  Could you please fill an issue on the github so that we won't forget the
  idea
  and will be able to discuss it.
 
  I don't think we will propose that feature for 1.0 but maybe it could be
  discussed for 2.0 :)
 
  regards,
  Bapt
 
 
 
 
 The issue has been created .
 
 During program writing , design and implementation at the beginning is much
 more easier than modifications
 performed after a completed design and implementation .
 
 

It is no more the begining of pkgng for long :)

Yes that is what we do, and because pkgng is very close to the doors we won't
break its design now, while we are ready to do it for 2.0 :)

regards,
Bapt


pgpbCiKsfQIxw.pgp
Description: PGP signature