ldapsh-devel Mailing List for LDAP shell (Page 2)
Status: Beta
Brought to you by:
rcorvalan
Menu
▾
▴
ldapsh-devel — Developpers of the tool
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(10) |
Jun
|
Jul
(3) |
Aug
(6) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rafael C. <Raf...@li...> - 2003-07-31 19:09:06
|
Hi,
I quicly saw the changes, they seem excellent. I'm leaving for holidays
(2 weeks), I think it would be a bad idea to try to aply the patches to
the HEAD right now. If I do something wrong, I won't be able to repair
that for 15 days.
I will do that in 2 weeks and a half. Or Peder, if you want and have
time too, you can incorporate the patches.
Peder, James, thanks a lot for your contributions. I have to change the
lines about the authors and contributors on the documentation.
Thanks a lot
Rafael
-----Original Message-----
From: James Devenish [mailto:j-d...@us...]=20
Sent: dimanche, 27. juillet 2003 12:03
To: lda...@li...
Subject: Re: [LDAPsh-devel] RE: ldapsh new features
Hi everyone,
I have made some changes to ldapsh in CVS. Some of these are "bug fixes"
and some are "new features". The "bug fixes" can be obtained by using
"cvs up -A". The new features are available within a series of CVS
branches as well as via the SourceForge patch tracker system:
<http://sourceforge.net/tracker/?group_id=3D54115&atid=3D472733>
One of the patches, the one regarding redirection (ID 778409), is not in
CVS because I don't really understand how 'redir' was supposed to work.
If anyone knows how to code Perl, please review and modify the new
features. When they are acceptable, they will hopefully be merged into
the main branch.
If you want to download all the bug fixes and new features (and you are
good with CVS), use the following series of CVS commands in this exact
order:
cvs up -kk -r 1.17 ldapsh && \
cvs up -kk -j 1.17 -j 1.17.2.1 ldapsh && \
cvs up -kk -j 1.17 -j 1.17.4.1 ldapsh && \
cvs up -kk -j 1.17 -j 1.17.6.1 ldapsh && \
cvs up -kkv -j 1.17 -j 1.20 ldapsh && \
cvs up -kk -j 1.20 -j 1.20.2.1 ldapsh && \
cvs up -kk -j 1.20 -j 1.20.4.1 ldapsh && \
cvs up -kk -j 1.20 -j 1.20.6.1 ldapsh
# now, edit the conflict by merely removing the conflict
# markers (and leaving all the new code in there!)
cvs up -kk -j 1.20 -j 1.20.8.1 ldapsh
(Note that this will leave 'sticky' tags on your CVS checkout. You can
later undo these by using `cvs up -A ldapsh`. Also, because Source-
Forge's CVS isn't working too well these days you might not be able to
connect with CVS.)
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01
/01
_______________________________________________
LDAPsh-devel mailing list
LDA...@li...
https://lists.sourceforge.net/lists/listinfo/ldapsh-devel
|
|
From: James D. <j-d...@us...> - 2003-07-27 10:03:22
|
Hi everyone,
I have made some changes to ldapsh in CVS. Some of these are "bug fixes"
and some are "new features". The "bug fixes" can be obtained by using
"cvs up -A". The new features are available within a series of CVS
branches as well as via the SourceForge patch tracker system:
<http://sourceforge.net/tracker/?group_id=54115&atid=472733>
One of the patches, the one regarding redirection (ID 778409), is not in
CVS because I don't really understand how 'redir' was supposed to work.
If anyone knows how to code Perl, please review and modify the new
features. When they are acceptable, they will hopefully be merged into
the main branch.
If you want to download all the bug fixes and new features (and you are
good with CVS), use the following series of CVS commands in this exact
order:
cvs up -kk -r 1.17 ldapsh && \
cvs up -kk -j 1.17 -j 1.17.2.1 ldapsh && \
cvs up -kk -j 1.17 -j 1.17.4.1 ldapsh && \
cvs up -kk -j 1.17 -j 1.17.6.1 ldapsh && \
cvs up -kkv -j 1.17 -j 1.20 ldapsh && \
cvs up -kk -j 1.20 -j 1.20.2.1 ldapsh && \
cvs up -kk -j 1.20 -j 1.20.4.1 ldapsh && \
cvs up -kk -j 1.20 -j 1.20.6.1 ldapsh
# now, edit the conflict by merely removing the conflict
# markers (and leaving all the new code in there!)
cvs up -kk -j 1.20 -j 1.20.8.1 ldapsh
(Note that this will leave 'sticky' tags on your CVS checkout. You can
later undo these by using `cvs up -A ldapsh`. Also, because Source-
Forge's CVS isn't working too well these days you might not be able to
connect with CVS.)
|
|
From: Rafael C. <Raf...@li...> - 2003-07-25 21:54:08
|
Hi James, OK, you're a member of the project, so you're able to checkout the project. Your proposal is excellent: " What I would suggest is: I could commit indentation and documentation updates to 'HEAD' (option 3), then commit new features into branches (option 2). I can then create diffs to put into the web tracker system (option 1). This would give maximum benefit to the widest range of people, I think. " Go ahead. I'm working on some new features, I will get the new indented version. Thanks a lot Rafael |
|
From: <po...@li...> - 2003-05-27 12:25:42
|
"Rafael Corvalan" <Raf...@li...> writes: > What do you usaually do? I do whatever cperl-mode in emacs defaults to :) I usually can't tell the difference between spaces and tabs, emacs hides it, but if I have to choose, I'd go for spaces. A space is a space is a space, which makes for a more predictable layout across different editors than do tabs. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: James D. <j-d...@us...> - 2003-05-27 12:21:25
|
In message <61F...@he...>
on Tue, May 27, 2003 at 02:13:41PM +0200, Rafael Corvalan wrote:
> So, one indent = 4 spaces, two indents = 1 TAB.
:)
> What do you usaually do?
My normal usage is ts=4, sw=4, noet. However, I customise my vim
settings according to the conventions of the project I am working
on. For example, I could have something like this in my .vimrc:
augroup ldapsh
autocmd BufEnter */ldapsh/* set ts=4 sw=4 et
autocmd BufLeave */ldapsh/* set ts=4 sw=4 noet
augroup end
|
|
From: <po...@li...> - 2003-05-27 12:18:33
|
"Rafael Corvalan" <Raf...@li...> writes: > Peder, since your patches are in production since a long time ago, I > think you can commit staight to HEAD. Ok, all my patches on sourceforge have now been committed, and their tracker items closed. > Thanks a lot for all your contributions. My pleasure. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: Rafael C. <Raf...@li...> - 2003-05-27 12:13:59
|
I think this is due to a misconfiguration of mi VIM editor. I configured a TS =3D 8 and Soft Tab Stop =3D 4. So, one indent =3D 4 spaces, two indents =3D 1 TAB. Bad idea.... What do you usaually do? -----Original Message----- From: James Devenish [mailto:j-d...@us...]=20 Sent: mardi, 27. mai 2003 14:08 To: Peder O. Klingenberg; Rafael Corvalan Cc: lda...@li... Subject: Re: ldapsh development For indentation of lines in the ldapsh script, there is a mixture of space and tabs. Perhaps a single style should be chosen? |
|
From: James D. <j-d...@us...> - 2003-05-27 12:07:50
|
For indentation of lines in the ldapsh script, there is a mixture of space and tabs. Perhaps a single style should be chosen? |
|
From: <po...@li...> - 2003-05-27 11:29:00
|
James Devenish <j-d...@us...> writes:
> * readline fixes -- essential.
I think so too. I think this should go into HEAD asap, even if we
decide to do further development in branches. Actually, IMO the
redirect patch is another HEAD candidate. Not being able to use '|'
or '>' in apply-expressions is quite limiting.
> * cp operation -- fabulous.
Thanks :)
> * can specify command-line perl instructions (handy for
> invoking the subroutine profiles that exist in rc files).
I'm not sure I understood this, but it sounds interesting. I'll
figure it out from the patch, I guess.
> * `add`, `replace`. `delete` as alternatives to `apply`.
Hm. 1-1 alternatives, or do they to $_->replace and $_->delete? And
how do you do add? I've missed an 'add' operation at times, but
worked around it using 'cp' and 'apply {$_->replace}'.
> I could do that next week or perhaps during the coming weekend.
> I would love for you to look over them.
Cool. Next week is rather busy for me, but I'll take a look when time
permits.
--
Peder O. Klingenberg | Systemkonsulent/Systems Consultant
Linpro AS | URL: http://www.linpro.no/
Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80
NO-0175 OSLO | Fax: +47 22 87 11 81
|
|
From: Rafael C. <Raf...@li...> - 2003-05-27 11:25:21
|
Here is the mail James sent to me on january with its patches. Rafael -----Original Message----- From: James Devenish [mailto:j-d...@us...]=20 Sent: dimanche, 26. janvier 2003 12:01 To: rco...@us... Subject: ldapsh new features and suggestions Hi, I recently discovered your ldapsh programme, hosted at SourceForge. It's "the answer to my prayers". But as a non Perl-brained person, I tend to struggle a bit with some software. I have the following suggestions that might make ldapsh a little more amenable to people who are not Perl enthusiasts. Please note that my Perl skills are minimal, so these may need refactoring. (1) Use the values of the $VISUAL or $EDITOR environment variables instead of requiring the user to add anything to his or her .ldapshrc (patch attached as ldapsh_1_editor). I also made a correction to a little typo in the docs. These variables are commonly used by other programmes (both BSD and SysV) so some users will have these set in their environment and expect them to be picked up. (2) I have a problem with GNU Readline on SOME/ALL platforms whereby your _resetTermReadline method causes echoing of the last-entered line. In the case that a password had just been entered, the echo includes the password in the clear. I have attached a patch (ldapsh_2_reset) in which the two "offending" lines are commented out (presumably leaving the function somewhat ineffectual). I don't know the solution to this but thought I should point it out. (3) I often wish to dump/list the entry whose DN is the current DN. For familiarity with regular 'ls' syntax, I have made a patch (ldapsh_3_dot) in which your <expansion> can now understand the full stop "." as meaning "the current DN" (or, more accurately, the search scope "base" rather than "sub" or "one"). I also added something to your regex so that a bare . gets quoted. This means "ls ." and "cat ." do something that I want. (4) I updated cd/pushd so that they can accept zero arguments gracefully (ldapsh_4_cd). cd will simply do nothing and pushd will, in effect, push the current directory. I updted the docs to reflect this. (5) I altered the main loop (see ldapsh_5_main) so that the user can usefully specify command-line arguments with ldapsh. That is, I can invoke `ldapsh profile_name` as a shortcut to invoking `ldapsh` and then entering 'profile_name' at the prompt. =20 (6) Added support (via ldapsh_6_edit) for three new commands: add, replace, delete. This are just shortcuts for the 'apply'-style manipulation of Net::LDAP::Entry. Though less powerful than 'apply', I think they are easier for general users. The patches are against CVS HEAD and will patch cleanly if applied in the order that I have listed them (though you can easily skip #2). Regards, James. |
|
From: Rafael C. <Raf...@li...> - 2003-05-27 11:23:42
|
Great for me. Peder, since your patches are in production since a long time ago, I think you can commit staight to HEAD. I will get the new HEAD at end of june, when I'll work again on it. Thanks a lot for all your contributions. Rafael -----Original Message----- From: Peder O. Klingenberg [mailto:po...@li...]=20 Sent: mardi, 27. mai 2003 12:16 To: Rafael Corvalan; James Devenish; lda...@li... Subject: Re: ldapsh development "Rafael Corvalan" <Raf...@li...> writes: > I propose giving you and Peder the rights to update CVS. At the end of > June, I will contribute with patches I have on my site since near 1=20 > year... >=20 > Let me know if that's OK for you. > Peder, also for you? Sure. I think I already have commit-rights, due to the ssh access to CVS, I just promised not to use it. I take this as a go-ahead to start committing. The patches I posted to sourceforge have been in production since they were posted. They seem stable, and ldapsh is now the main user administration tool at a customer site. James, have you looked at those patches? Are they ok with you? Any objections to committing those, from either of you? Also, James, what are the patches you have? Do you mind posting them to sf so I can have a look? Rafael, how do you prefer we do the commits? Should we commit straight to HEAD, or should we branch out? (I've added ldapsh-devel to the to-list. I like the archives on sf, and it helps me sort my mail.) --=20 Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: James D. <j-d...@us...> - 2003-05-27 10:34:33
|
In message <uju...@ta...> on Tue, May 27, 2003 at 12:15:39PM +0200, Peder O. Klingenberg wrote: > James, have you looked at those patches? Are they ok with you? Any > objections to committing those, from either of you? All LDAP-accessible directories that I use have been mostly stable for the last month, so I have merely been doing casual queries with ldapsh. Thus, my recollection of editing features and code patches is a little hazy. From what I recall: * readline fixes -- essential. * cp operation -- fabulous. * other patches -- unused. > Also, James, what are the patches you have? * honour $VISUAL and $EDITOR from environment. * easy search recall. * documentation modifications. * '.' expression syntax (e.g `ls .`, `cat .`) as shorthand for "the current DN". * cd/pushd more like sh. * can specify command-line perl instructions (handy for invoking the subroutine profiles that exist in rc files). * `add`, `replace`. `delete` as alternatives to `apply`. > Do you mind posting them to sf so I can have a look? I could do that next week or perhaps during the coming weekend. I would love for you to look over them. |
|
From: <po...@li...> - 2003-05-27 10:16:39
|
"Rafael Corvalan" <Raf...@li...> writes: > I propose giving you and Peder the rights to update CVS. At the end of > June, I will contribute with patches I have on my site since near 1 > year... > > Let me know if that's OK for you. > Peder, also for you? Sure. I think I already have commit-rights, due to the ssh access to CVS, I just promised not to use it. I take this as a go-ahead to start committing. The patches I posted to sourceforge have been in production since they were posted. They seem stable, and ldapsh is now the main user administration tool at a customer site. James, have you looked at those patches? Are they ok with you? Any objections to committing those, from either of you? Also, James, what are the patches you have? Do you mind posting them to sf so I can have a look? Rafael, how do you prefer we do the commits? Should we commit straight to HEAD, or should we branch out? (I've added ldapsh-devel to the to-list. I like the archives on sf, and it helps me sort my mail.) -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: <po...@li...> - 2002-11-24 11:37:11
|
I just uploaded a patch that fixes the annoying issue of readline echoing your password if you mistype it. Rafael, are your reading this list anymore? I have a couple of older patches uploaded as well, which I announced on this list. I haven't heard anything, and I wonder if you're still here. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: <po...@li...> - 2002-10-28 12:15:42
|
Three, to be exact. The first is a bit of further development on the cp command, it can now copy across trees. The second patch implements two small helper-routines to aid in communicating with users in interactive routines. I'm currently implementing some more complex site specific commands in /etc/ldapshrc, and needed to communicate with the user. Last, but not least, the redirect code bit me when I was trying to send an anonymous hash-ref as an argument to a command (I like using =>). I uploaded a patch that requires the > or | to be preceeded by a ;, which I believe resolves most ambiguities. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: <po...@li...> - 2002-09-09 10:56:03
|
I just uploaded a new patch implementing a copy operation for entries. It needs a bit of work, but should be ok as a starting point. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: Rafael C. <Raf...@li...> - 2002-07-31 15:53:18
|
Hello, I created the "CVS Commit mailing list": lda...@li... Subscribers to this list will be notified on any commit. Rafael |
|
From: <po...@li...> - 2002-07-31 09:41:48
|
In the ldapsh doc, AUTHOR section, you are listed with the mail address <raf...@ne...>. I notice you're not sending mail with that address, is it still valid? -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: <po...@li...> - 2002-07-31 09:39:01
|
"Rafael Corvalan" <Raf...@li...> writes: > You are now a "developper" of the project, I hope this will be enough... > The doc is not really clear, there is an inconsistency between the doc > and the screens shown... Thank you. Yes, that was enough. > In the mid-time, you can get all the files using "cvs -dXXXXXXX co ." Ah, of course. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: Rafael C. <Raf...@li...> - 2002-07-31 08:50:10
|
Peder, You are now a "developper" of the project, I hope this will be enough... The doc is not really clear, there is an inconsistency between the doc and the screens shown... I asked sourceforge admin to move the files in the CVS repository (only sourceforge staff can do so). See http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D588998&group= _id =3D1&atid=3D200001 I've done so because I think this is a good thnig. "ldapsh" will be a CVS "module", and I will create a new module "buil-rel" where I will put the scripts I have to build the releases (run pod2html, generate tarballs etc...). In the mid-time, you can get all the files using "cvs -dXXXXXXX co ." Rafael |
|
From: <po...@li...> - 2002-07-30 15:51:34
|
"Rafael Corvalan" <Raf...@li...> writes: > What do you expect exactly? Do you want me to create a > ldapsh directory under /cvsroot/ldapsh? So you can do: > cvs -d:pserver:ano...@cv...:/cvsroot/ldapsh co ldapsh ? That would look more like the other projects I've seen, yes. > Because I tried your setting: > "cvs -d:pserver:anonymous@...sf.net:/cvsroot/ co " > but I don't understand how can it works since /cvsroot is > not owned by me... No, that won't work. I tried that as well :) > I'm not familiar with sourceforge environment, but if you point > me to a doc which explains how to do so, I'd be happy ;-))) Basically, I think the only way to grant ssh access to CVS is to make someone a developer on your project. I assume you can do that from the Admin pages on the project page. I'm a bit fuzzy on the details, because I'm not an admin of any sourceforge projects, so I've never seen those pages. The drawback is that making someone a developer grants commit rights as well, which you may not want to give out. But I'm asking anyway: can you make me a developer on ldapsh? I promise I won't commit anything without permission. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
|
From: Rafael C. <Raf...@li...> - 2002-07-30 15:38:34
|
In reply to message from Peder O. Klingenberg: --------------- Hello Peder, > An idea for the longer term is to support > #!/usr/bin/ldapsh and write scripts in > ldapsh syntax This is a good idea. I had another idea is to make ldapsh a module and a script. The script just beeing something like "use LDAPsh; shell;". Just like CPAN does. > I'll be uploading a couple of patches to sourceforge > in a moment (nothing big, just details). I applied 2 of them. The "diff1" patch should be updated to allow users to choose the encryption SSL or TLS. In fact, my ADS and OpenLDAP car do SSL, but are not setup to do TLS... I'm probably not the only one... > One thing I'm seeing which I'm not quite sure how > to fix yet is the ReadLine::GNU password handling. > My xterm prints funny characters around the "Password:" > prompt, and if I type the wrong password, it's echoed > back at me. Several times, in fact. Anyone else seeing > this? I'll be looking at it in more detail later on. I already saw something similar with some terminals. I think it's closely related to ReadLine::GNU and I didn't go more in-depth to see where does the problem comes from. > Two questions: Why is the CVS structure as it is? > It's impossible to check out the project as a module > using anonymous pserver, I had to check out each file > explicitly. Other sf projects I have worked on have > their files under /cvsroot//, so that > 'cvs -d:pserver:anonymous@...sf.net:/cvsroot/ co ' > work. The only reason is: ignorance ;-) I didn't though on that issue. I don't understand very well sourceforge architecture so I just followed the recommendations I found on one of the docs. What do you expect exactly? Do you want me to create a ldapsh directory under /cvsroot/ldapsh? So you can do: cvs -d:pserver:ano...@cv...:/cvsroot/ldapsh co ldapsh ? Because I tried your setting: "cvs -d:pserver:anonymous@...sf.net:/cvsroot/ co " but I don't understand how can it works since /cvsroot is not owned by me... > Next: What does it take to get ssh access to ldapsh cvs? I'm > currently behind a firewall that does not allow pserver through. To > do anything useful I have to check out ldapsh to another machine, and > scp files through the firewall, which is kind of a hassle. I'm not familiar with sourceforge environment, but if you point me to a doc which explains how to do so, I'd be happy ;-))) Thanks a lot Rafael |
|
From: <po...@li...> - 2002-07-30 11:33:47
|
(Are these mailinglists in use at all?) Thank you for a slick product. I had just started to write my own ldapsh when I found yours, which was far more complete than my 1-day hack. The code was generally a pleasure to work with as well. I will (eventually) be using this in a mixed environment of Solaris and Linux systems, using openLDAP to manage users, groups and login rights. I suspect I'll be writing quite a few local commands to do the higher level stuff. An idea for the longer term is to support #!/usr/bin/ldapsh and write scripts in ldapsh syntax. I'll be uploading a couple of patches to sourceforge in a moment (nothing big, just details). One thing I'm seeing which I'm not quite sure how to fix yet is the ReadLine::GNU password handling. My xterm prints funny characters around the "Password:" prompt, and if I type the wrong password, it's echoed back at me. Several times, in fact. Anyone else seeing this? I'll be looking at it in more detail later on. Two questions: Why is the CVS structure as it is? It's impossible to check out the project as a module using anonymous pserver, I had to check out each file explicitly. Other sf projects I have worked on have their files under /cvsroot/<projname>/<projname>, so that 'cvs -d:pserver:anonymous@...sf.net:/cvsroot/<projname> co <projname>' work. Next: What does it take to get ssh access to ldapsh cvs? I'm currently behind a firewall that does not allow pserver through. To do anything useful I have to check out ldapsh to another machine, and scp files through the firewall, which is kind of a hassle. -- Peder O. Klingenberg | Systemkonsulent/Systems Consultant Linpro AS | URL: http://www.linpro.no/ Wdm. Thranes Gt 98b | Tlf: +47 22 87 11 80 NO-0175 OSLO | Fax: +47 22 87 11 81 |
