Thread: Re: [A-A-P-develop] :action depend for D
Brought to you by:
vimboss
From: Bram M. <Br...@mo...> - 2003-10-30 13:22:25
|
Lars Ivar Igesund wrote: > I have now created a dependency checker for D (in D). > Attached is a diff for d.aap (adds action depend, and an > :assertpkg for the dependencychecker). The depend > action is tested and works on Windows (no reason it > shouldn't work in Linux, but it isn't tested yet). Very good to see you made this! > Also attached is a minor doc change to ref-modules, > since the DIMPORTS variable is used by the depchecker. > > And also attached is the depchkd src and a bootscript > (I have no idea if it works...) If you don't want to host > depchkd, I can do that myself. It might offload you from > needing to update depchkd when it changes (and it will > change). If you have an account on sourceforge I can give you permission to update the files yourself. Just promise you won't touch any of the other files (my upload script will overwrite them anyway...). But if you have a good place to host the files yourself, the package recipe on the A-A-P site can redirect to that. A few remarks: I typed the name wrong a few times. The name "depchkd" could be "depcheckd". Or perhaps "ddepcheck"? It's not that important, but once it's chosen it's difficult to change without causing trouble. The bootstrap recipe for the package downloads the source, compiles it and moves it to the Aap bin directory. It looks like you didn't test this: There is no "Global.aap_srcdir". You can download the file into the current directory and build it there. Compiling depchekd.d is done by directly invoking "dmd". This bypasses the carefully tuned "d" module and "dmd" tool. How about doing it very simple: :import d bindir = "`Global.aap_bindir`" :program $bindir/depchkd : depchkd.d {fetch = http://www.a-a-p.org/packages/%file%} Does that work? Hmm, we have a chicken/egg problem here: The package recipe includes the "d" module to be able to build the depchkd program, but the "d" module wants to use the "depchkd" program! I guess your method to invoke "dmd" directly wasn't such a bad idea. How about this then: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- bindir = "`Global.aap_bindir`" :mkdir {force} $bindir all: :print This will build depchkd. :fetch {fetch = http://www.a-a-p.org/packages/%file%} depchkd.d :progsearch dc dmd :sys $dc depchkd.d :del depchkd.d install: :print This will install depchkd. :move {force} depchkd$EXESUF $bindir -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I have uploaded this, thus you can try it out with "aap --install depchkd". -- An indication you must be a manager: You give constructive feedback to your dog. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |
From: Lars I. I. <lar...@ig...> - 2003-10-31 07:55:29
|
----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> > But if you have a good place to host the files yourself, the package > recipe on the A-A-P site can redirect to that. I have a good and stable place. It will be natural to have it there for others anyway. It is now situated at http://www.igesund.net/larsivar/ddepcheck.d > > A few remarks: > > I typed the name wrong a few times. The name "depchkd" could be > "depcheckd". Or perhaps "ddepcheck"? It's not that important, but once > it's chosen it's difficult to change without causing trouble. As you see, I've changed it to ddepcheck > > The bootstrap recipe for the package downloads the source, compiles it > and moves it to the Aap bin directory. It looks like you didn't test > this: There is no "Global.aap_srcdir". You can download the file into > the current directory and build it there. No I didn't test it :) > > Compiling depchekd.d is done by directly invoking "dmd". This bypasses > the carefully tuned "d" module and "dmd" tool. Yes I'm aware. As long as dmd is the only compiler, it's not really a problem. It has to be installed anyway (maybe using ":assertpkg {optional}" first). > I guess your method to invoke "dmd" directly wasn't such a bad idea. It wasn't ;) > How about this then: > :sys $dc depchkd.d I think we will optimize: :sys $dc -O ddepcheck.d > > I have uploaded this, thus you can try it out with "aap --install > depchkd". Ok, the fetching and installing works as a charm. The problem though with it being installed in bindir, is that :sys don't find at since that dir isn't in PATH. :assertpkg do, though. Some possible solutions. 1. Have the boot.aap install it somewhere that we *knows* is in PATH. (I don't like this solution). 2. Instruct the user to add bindir to PATH. (Not automatic enough?) 3. Add bindir to PATH automatically at some time. (Shell (atleast cmd.exe) must be restarted before it works) 4. Let :sys check bindir too. (A possibly ugly solution?) 5. Let the user provide a directory during install. (It is then up to the user to make sure the dir is in PATH) Lars Ivar Igesund |
From: Bram M. <Br...@mo...> - 2003-10-31 11:22:18
|
Lars Ivar Igesund wrote: > From: "Bram Moolenaar" <Br...@mo...> > > But if you have a good place to host the files yourself, the package > > recipe on the A-A-P site can redirect to that. > > I have a good and stable place. It will be natural to have it there > for others anyway. It is now situated at > http://www.igesund.net/larsivar/ddepcheck.d Good. I'll adjust the package recipe to download that file. > > A few remarks: > > > > I typed the name wrong a few times. The name "depchkd" could be > > "depcheckd". Or perhaps "ddepcheck"? It's not that important, but once > > it's chosen it's difficult to change without causing trouble. > > As you see, I've changed it to ddepcheck OK, I'll change the d module. Note that I'm currently releasing versions in CVS only, until we worked out the details. > > The bootstrap recipe for the package downloads the source, compiles it > > and moves it to the Aap bin directory. It looks like you didn't test > > this: There is no "Global.aap_srcdir". You can download the file into > > the current directory and build it there. > > No I didn't test it :) > > > Compiling depchekd.d is done by directly invoking "dmd". This bypasses > > the carefully tuned "d" module and "dmd" tool. > > Yes I'm aware. As long as dmd is the only compiler, it's not really a > problem. It has to be installed anyway (maybe using ":assertpkg > {optional}" first). There is also a problem for people that don't have an internet connection. They would not get past this :assertpkg. Adding {optional} is possible, but then dependency checking doesn't work... Is giving a warning sufficient? Otherwise, the file could be included in the distribution somehow. > > I guess your method to invoke "dmd" directly wasn't such a bad idea. > > It wasn't ;) > > > How about this then: > > > :sys $dc depchkd.d > I think we will optimize: > :sys $dc -O ddepcheck.d OK, I'll add the "-O". > > I have uploaded this, thus you can try it out with "aap --install > > depchkd". > > Ok, the fetching and installing works as a charm. The problem though > with it being installed in bindir, is that :sys don't find at since that dir > isn't in PATH. :assertpkg do, though. Some possible solutions. > > 1. Have the boot.aap install it somewhere that we *knows* is in PATH. > (I don't like this solution). > > 2. Instruct the user to add bindir to PATH. > (Not automatic enough?) > > 3. Add bindir to PATH automatically at some time. > (Shell (atleast cmd.exe) must be restarted before it works) > > 4. Let :sys check bindir too. > (A possibly ugly solution?) > > 5. Let the user provide a directory during install. > (It is then up to the user to make sure the dir is in PATH) The Aap way of doing this is to use: :progsearch DDEPCHECK ddepcheck And then use ":sys $DDEPCHECK ..." I tried using $m_d.DDEPCHECK but that apparently doesn't work... -- ARTHUR: No, hang on! Just answer the five questions ... GALAHAD: Three questions ... ARTHUR: Three questions ... And we shall watch ... and pray. "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |
From: Lars I. I. <lar...@ig...> - 2003-10-31 11:34:25
|
----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> > > There is also a problem for people that don't have an internet > connection. They would not get past this :assertpkg. Adding {optional} > is possible, but then dependency checking doesn't work... Is giving a > warning sufficient? Otherwise, the file could be included in the > distribution somehow. Well, the license allows it :) It is about 10k, but for aap's purposes it don't need to be that large. Maybe a reduced version could be included in case there is no connection and it isn't present othervise? > > > I have uploaded this, thus you can try it out with "aap --install > > > depchkd". > > > > Ok, the fetching and installing works as a charm. The problem though > > with it being installed in bindir, is that :sys don't find at since that dir > > isn't in PATH. :assertpkg do, though. Some possible solutions. > > > > 1. Have the boot.aap install it somewhere that we *knows* is in PATH. > > (I don't like this solution). > > > > 2. Instruct the user to add bindir to PATH. > > (Not automatic enough?) > > > > 3. Add bindir to PATH automatically at some time. > > (Shell (atleast cmd.exe) must be restarted before it works) > > > > 4. Let :sys check bindir too. > > (A possibly ugly solution?) > > > > 5. Let the user provide a directory during install. > > (It is then up to the user to make sure the dir is in PATH) > > The Aap way of doing this is to use: > > :progsearch DDEPCHECK ddepcheck > > And then use ":sys $DDEPCHECK ..." Ah, of course. And this works. Lars Ivar Igesund |
From: Bram M. <Br...@mo...> - 2003-10-31 11:49:18
|
Lars Ivar Igesund wrote: > From: "Bram Moolenaar" <Br...@mo...> > > > > There is also a problem for people that don't have an internet > > connection. They would not get past this :assertpkg. Adding {optional} > > is possible, but then dependency checking doesn't work... Is giving a > > warning sufficient? Otherwise, the file could be included in the > > distribution somehow. > > Well, the license allows it :) It is about 10k, but for aap's purposes it > don't need to be that large. Maybe a reduced version could be > included in case there is no connection and it isn't present othervise? This would be possible, but then it can't try to install a package at the same time. Thus the d module would have to check if "ddepcheck" can be found and when not: build it from the included ddpecheck.d. An alternative is to implement the dependency checker in Python. Then it doesn't need to be compiled and installed first. It will be a lot slower though. You would have to send me ddepcheck.d each time you make improvements. The user could still do "aap --install ddepcheck" to obtain an updated version. -- BEDEVERE: How do you know so much about swallows? ARTHUR: Well you have to know these things when you're a king, you know. "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |
From: Lars I. I. <lar...@ig...> - 2003-11-01 09:39:29
|
----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> Well, the best would be if everybody could get themselves an internet connection. ;) > This would be possible, but then it can't try to install a package at > the same time. Thus the d module would have to check if "ddepcheck" can > be found and when not: build it from the included ddpecheck.d. > > An alternative is to implement the dependency checker in Python. Then > it doesn't need to be compiled and installed first. It will be a lot > slower though. This might be an acceptable solution since it is very likely that most people using aap for D will have an internet connection. I can try to implement this when I get the time, and have it as it as for the moment. Unless you think inclusion of ddepcheck is the best. The python version would need the same updates in any case. (The necessary changes are mostly related to changes/additions to the runtime library as ddepcheck don't consider these as dependencies (kinda like system headers)). After thinking some more I'm positive that inclusion of ddepcheck.d is better than implementing it in Python. > > You would have to send me ddepcheck.d each time you make improvements. No problem, really. > The user could still do "aap --install ddepcheck" to obtain an updated > version. Yes. Lars Ivar Igesund |
From: Bram M. <Br...@mo...> - 2003-11-01 12:34:13
|
Lars Ivar Igesund wrote: > Well, the best would be if everybody could get themselves an internet > connection. ;) I'm sometimes using my notebook on a plane... > > This would be possible, but then it can't try to install a package at > > the same time. Thus the d module would have to check if "ddepcheck" can > > be found and when not: build it from the included ddpecheck.d. > > > > An alternative is to implement the dependency checker in Python. Then > > it doesn't need to be compiled and installed first. It will be a lot > > slower though. > > This might be an acceptable solution since it is very likely that most > people using aap for D will have an internet connection. I can try to > implement this when I get the time, and have it as it as for the > moment. Unless you think inclusion of ddepcheck is the best. The > python version would need the same updates in any case. (The necessary > changes are mostly related to changes/additions to the runtime library > as ddepcheck don't consider these as dependencies (kinda like system > headers)). After thinking some more I'm positive that inclusion of > ddepcheck.d is better than implementing it in Python. > > > You would have to send me ddepcheck.d each time you make improvements. > > No problem, really. > > > The user could still do "aap --install ddepcheck" to obtain an updated > > version. > > Yes. Making a Python implementation would be a lot more work, and its speed would be disappointing. So let's forget about that. Including ddepcheck.d with Aap sounds like a good solution. Even better would be if the D compiler would be able to do this by itself, like gcc does. But that's not in our hands. Please look at the current version in CVS and suggest how ddepcheck.d can be added and compiled when necessary. I think it needs to go into the "tools" directory. -- Men may not be seen publicly in any kind of strapless gown. [real standing law in Florida, United States of America] /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |
From: Lars I. I. <lar...@ig...> - 2003-11-05 09:28:37
Attachments:
ddepcheck.d
d.diff
|
----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> > I'm sometimes using my notebook on a plane... Well, they should get internet in the planes then :) > Making a Python implementation would be a lot more work, and its speed > would be disappointing. So let's forget about that. Good. > Including ddepcheck.d with Aap sounds like a good solution. Even better > would be if the D compiler would be able to do this by itself, like gcc > does. But that's not in our hands. Well, at the moment, there is only one man working on a/(the) compiler, making such features very low priority. He can bundle my ddepcheck, if he want to, though. > > Please look at the current version in CVS and suggest how ddepcheck.d > can be added and compiled when necessary. I think it needs to go into > the "tools" directory. Ok, attached is the newest version of ddepcheck to be put into the tools dir. Also attached is the patch for d.aap that builds ddepcheck in case it couldn't be downloaded. Possibly it looks a bit hairy, but it works. Also, for the bootscript, could you add the files ddepcheck$OBJSUF and ddepcheck.map to the files to be deleted afterwards? (see the d.aap patch for what I mean.) Well, it's getting there :) Lars Ivar Igesund |
From: Lars I. I. <lar...@ig...> - 2003-11-05 11:01:59
Attachments:
ddepcheck.d
|
Another minor change to ddepcheck. Hopefully the last for a while. Lars Ivar Igesund ----- Original Message ----- From: "Lars Ivar Igesund" <lar...@ig...> To: <a-a...@li...> Sent: Wednesday, November 05, 2003 10:32 AM Subject: Re: [A-A-P-develop] :action depend for D > ----- Original Message ----- > From: "Bram Moolenaar" <Br...@mo...> > > > I'm sometimes using my notebook on a plane... > > Well, they should get internet in the planes then :) > > > Making a Python implementation would be a lot more work, and its speed > > would be disappointing. So let's forget about that. > > Good. > > > Including ddepcheck.d with Aap sounds like a good solution. Even better > > would be if the D compiler would be able to do this by itself, like gcc > > does. But that's not in our hands. > > Well, at the moment, there is only one man working on a/(the) compiler, > making such features very low priority. He can bundle my ddepcheck, if > he want to, though. > > > > > Please look at the current version in CVS and suggest how ddepcheck.d > > can be added and compiled when necessary. I think it needs to go into > > the "tools" directory. > > Ok, attached is the newest version of ddepcheck to be put into the tools > dir. > Also attached is the patch for d.aap that builds ddepcheck in case it > couldn't > be downloaded. Possibly it looks a bit hairy, but it works. > > Also, for the bootscript, could you add the files > ddepcheck$OBJSUF and ddepcheck.map to the files to be deleted > afterwards? (see the d.aap patch for what I mean.) > > Well, it's getting there :) > > Lars Ivar Igesund > |
From: Bram M. <Br...@mo...> - 2003-11-05 11:16:59
|
Lars Ivar Igesund wrote: > > I'm sometimes using my notebook on a plane... > > Well, they should get internet in the planes then :) I tried, but couldn't get the cable through the security check. :-) > > Please look at the current version in CVS and suggest how ddepcheck.d > > can be added and compiled when necessary. I think it needs to go into > > the "tools" directory. > > Ok, attached is the newest version of ddepcheck to be put into the tools > dir. I notice you use Global.aap_toolsdir. That didn't exist yet! I'll add it to Global.py. To be consistent I'll also add aap_modulesdir. > Also attached is the patch for d.aap that builds ddepcheck in case it > couldn't be downloaded. Possibly it looks a bit hairy, but it works. > > Also, for the bootscript, could you add the files > ddepcheck$OBJSUF and ddepcheck.map to the files to be deleted > afterwards? (see the d.aap patch for what I mean.) Apparently the compiler produces these files without asking. It's OK to delete them. Just make sure the compiler won't overwrite something. To make sure failure in compiling the program is detected, I suggest using this: # If not downloaded, build it from local copy. :progsearch _top.DDEPCHECK ddepcheck @if not _top.DDEPCHECK: bindir = "`Global.aap_bindir`" toolsdir = "`Global.aap_toolsdir`" :mkdir {force} $bindir :print ddepcheck not found, building from: $toolsdir/ddepcheck.d :progsearch dc dmd :sys $dc -O -of$bindir`os.sep`ddepcheck$EXESUF $toolsdir`os.sep`ddepcheck.d :del {q} ddepcheck$OBJSUF ddepcheck.map :progsearch _top.DDEPCHECK ddepcheck @if not _top.DDEPCHECK: :error Building ddepcheck failed or the program cannot be found. Now, there is one remaining problem: Aap may be installed on the system and the directories are not writable by a normal user. The best solution I can think of is to offer the user a choice: - become root and install ddepcheck globally (using :asroot) - install for the current user only (in $HOME/bin) - quit BTW: Is there a Vim syntax highlighting file for the D language? -- Mynd you, m00se bites Kan be pretty nasti ... "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |
From: Lars I. I. <lar...@ig...> - 2003-11-05 23:13:08
|
----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> > > I notice you use Global.aap_toolsdir. That didn't exist yet! I'll add > it to Global.py. To be consistent I'll also add aap_modulesdir. Yes, I forgot to attach the patch. It was so easy I forgot that I made the change! > > > Also attached is the patch for d.aap that builds ddepcheck in case it > > couldn't be downloaded. Possibly it looks a bit hairy, but it works. > > > > Also, for the bootscript, could you add the files > > ddepcheck$OBJSUF and ddepcheck.map to the files to be deleted > > afterwards? (see the d.aap patch for what I mean.) > > Apparently the compiler produces these files without asking. It's OK to > delete them. Just make sure the compiler won't overwrite something. > > To make sure failure in compiling the program is detected, I suggest > using this: > > # If not downloaded, build it from local copy. > :progsearch _top.DDEPCHECK ddepcheck > > @if not _top.DDEPCHECK: > bindir = "`Global.aap_bindir`" > toolsdir = "`Global.aap_toolsdir`" > :mkdir {force} $bindir > :print ddepcheck not found, building from: $toolsdir/ddepcheck.d > :progsearch dc dmd > :sys $dc -O -of$bindir`os.sep`ddepcheck$EXESUF $toolsdir`os.sep`ddepcheck.d > :del {q} ddepcheck$OBJSUF ddepcheck.map > :progsearch _top.DDEPCHECK ddepcheck > @if not _top.DDEPCHECK: > :error Building ddepcheck failed or the program cannot be found. > > Now, there is one remaining problem: Aap may be installed on the system > and the directories are not writable by a normal user. The best > solution I can think of is to offer the user a choice: > > - become root and install ddepcheck globally (using :asroot) > - install for the current user only (in $HOME/bin) > - quit Hmm, sounds ok. Should I do this or are you onto it? > > BTW: Is there a Vim syntax highlighting file for the D language? AFAIK the only one is this: http://www.vim.org/scripts/script.php?script_id=379 It is very simple and outdated. But it's the one I use with a couple of keyword additions (foreach at least). Why? Do you want to program in D? Or do you want me to make a better one? Lars Ivar Igesund |
From: Bram M. <Br...@mo...> - 2003-11-07 13:11:30
|
Lars Ivar Igesund wrote: > > Now, there is one remaining problem: Aap may be installed on the system > > and the directories are not writable by a normal user. The best > > solution I can think of is to offer the user a choice: > > > > - become root and install ddepcheck globally (using :asroot) > > - install for the current user only (in $HOME/bin) > > - quit > > Hmm, sounds ok. Should I do this or are you onto it? It would be better if you do it, since you can try it out. If you need examples, look in the packages on http://www.a-a-p.org/packages > > BTW: Is there a Vim syntax highlighting file for the D language? > > AFAIK the only one is this: > http://www.vim.org/scripts/script.php?script_id=379 > > It is very simple and outdated. But it's the one I use with a couple > of keyword additions (foreach at least). Why? Do you want to > program in D? Or do you want me to make a better one? I was looking at ddepcheck.d and found it quite boring :-). Jason, could you send me the latest version of the D syntax highlighing file? I could include it in the Vim distribution then. -- CART DRIVER: Bring out your dead! LARGE MAN: Here's one! CART DRIVER: Ninepence. BODY: I'm not dead! "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |
From: Lars I. I. <lar...@ig...> - 2003-11-08 11:49:44
Attachments:
ddepcheck.d
|
A new version of ddepcheck.d ----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> To: "Lars Ivar Igesund" <lar...@ig...> Cc: <a-a...@li...>; <jm...@cs...> Sent: Friday, November 07, 2003 2:09 PM Subject: Re: [A-A-P-develop] :action depend for D > > Lars Ivar Igesund wrote: > > > > Now, there is one remaining problem: Aap may be installed on the system > > > and the directories are not writable by a normal user. The best > > > solution I can think of is to offer the user a choice: > > > > > > - become root and install ddepcheck globally (using :asroot) > > > - install for the current user only (in $HOME/bin) > > > - quit > > > > Hmm, sounds ok. Should I do this or are you onto it? > > It would be better if you do it, since you can try it out. If you need > examples, look in the packages on http://www.a-a-p.org/packages > > > > BTW: Is there a Vim syntax highlighting file for the D language? > > > > AFAIK the only one is this: > > http://www.vim.org/scripts/script.php?script_id=379 > > > > It is very simple and outdated. But it's the one I use with a couple > > of keyword additions (foreach at least). Why? Do you want to > > program in D? Or do you want me to make a better one? > > I was looking at ddepcheck.d and found it quite boring :-). > > Jason, could you send me the latest version of the D syntax highlighing > file? I could include it in the Vim distribution then. > > -- > CART DRIVER: Bring out your dead! > LARGE MAN: Here's one! > CART DRIVER: Ninepence. > BODY: I'm not dead! > "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD > > /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ > /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ > \\\ Project leader for A-A-P -- http://www.A-A-P.org /// > \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > A-A-P-develop mailing list > A-A...@li... > https://lists.sourceforge.net/lists/listinfo/a-a-p-develop > |
From: Lars I. I. <lar...@ig...> - 2003-11-12 10:33:56
|
----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> > > > Now, there is one remaining problem: Aap may be installed on the system > > > and the directories are not writable by a normal user. The best > > > solution I can think of is to offer the user a choice: > > > > > > - become root and install ddepcheck globally (using :asroot) > > > - install for the current user only (in $HOME/bin) > > > - quit > > > > Hmm, sounds ok. Should I do this or are you onto it? Ok, the d.diff patch do something like this and it works (on Windows). I'm not sure what I should use when installing globally (so I didn't) and why should I use $HOME instead of aapdir/bin? In both cases I have used aapdir/bin, just using :asroot if necessary. Please modify as needed (so I can learn from my mistakes :) Also, a patch for a modified ddepcheck is included (at least one serious bug was fixed (deep recursion stuff), and a couple of buglets). It's been "optimized" too (actually it was the deep recursion fix), and it don't slow down for deep import trees. Interestingly (or strangely), cvs diff -/+ all of the code, so the patch is bigger than the actual source :) And a minor doc patch (I feel that I understand 'commit' better than 'commot'). Lars Ivar Igesund |
From: Bram M. <Br...@mo...> - 2003-11-12 17:01:18
|
Lars Ivar Igesund wrote: > > > > Now, there is one remaining problem: Aap may be installed on the > > > > system and the directories are not writable by a normal user. > > > > The best solution I can think of is to offer the user a choice: > > > > > > > > - become root and install ddepcheck globally (using :asroot) > > > > - install for the current user only (in $HOME/bin) > > > > - quit > > > > > > Hmm, sounds ok. Should I do this or are you onto it? > > Ok, the d.diff patch do something like this and it works (on Windows). > I'm not sure what I should use when installing globally (so I didn't) and > why should I use $HOME instead of aapdir/bin? In both cases I have > used aapdir/bin, just using :asroot if necessary. Please modify as > needed (so I can learn from my mistakes :) I didn't try it, but it looks like it should work OK if the user can become root when necessary. But it won't work for an ordinary user. I'm not sure how to solve this. We should offer the choice whether the user wants to become root and install globally, or install in his home directory only. But that last option is something new, I don't know what directory to use then. ~/bin would be obvious, but not everybody has that in $PATH. Another solution would be to install Aap for the user, so that he can write in the Aap directories. But that sounds like a clumsy solution... > Also, a patch for a modified ddepcheck is included (at least one > serious bug was fixed (deep recursion stuff), and a couple of > buglets). It's been "optimized" too (actually it was the deep > recursion fix), and it don't slow down for deep import trees. > Interestingly (or strangely), cvs diff -/+ all of the code, so the patch > is bigger than the actual source :) Looks like some trouble with line endings. My patch program didn't complain, thus I included this patch without trouble. > And a minor doc patch (I feel that I understand 'commit' better than > 'commot'). I'll include that as well. Thanks! -- hundred-and-one symptoms of being an internet addict: 1. You actually wore a blue ribbon to protest the Communications Decency Act. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |
From: Lars I. I. <lar...@ig...> - 2003-11-13 09:06:21
Attachments:
d.diff
|
----- Original Message ----- From: "Bram Moolenaar" <Br...@mo...> > > I didn't try it, but it looks like it should work OK if the user can > become root when necessary. But it won't work for an ordinary user. > I'm not sure how to solve this. We should offer the choice whether the > user wants to become root and install globally, or install in his home > directory only. But that last option is something new, I don't know > what directory to use then. ~/bin would be obvious, but not everybody > has that in $PATH. I've attached a diff for what I think is the best solution or at least on the path to the best solution. What do you think? It worked as expected for me. I haven't tested it thouroughly though. > > Looks like some trouble with line endings. My patch program didn't > complain, thus I included this patch without trouble. Ah, yes. It stopped by a windows prog before I diffed. Lars Ivar Igesund |