Re: wiki issues inregards to fetching plugins
On Mon, 2007-03-12 at 22:17 +0100, Peter J. Holzer wrote: > > The problem is that almost no-one has access (which you did explain to > > me in response to my code.google tracker) so the wiki is being used as a > > source code repository. This is the only problem that I see. > > I've have several times offered to act as a "human gateway" to the > contrib directory. That is, I will add a subdirectory below contrib for > anyone who asks and check in and update plugins people send to me. > So far nobody has taken me up on that offer. I will when/if I get there ... but I'm being much slower than I anticipated ... > > (Yes, a repository where everybody could have write access to their own > subtree would be better - but as long as there are only two people who > have contributed anything (and at least one of them (me) has commit Ok. > rights anyway) I can understand that the repository owners don't want to > invest work into the svn infrastructure.) Ask says he has given svn access to anyone who has asked so I don't see any problem here. I suppose I will request access if and when I require it. Until then I will just send things your way. When I get back to looking at the wiki, I suppose I could copy plugin code, test it, track down the originator and send it to you to be put in the appropriate place. As long as that works, I can then replace the wiki text with a pointer to the svn repo. Unless someone complains ... -- --gh
Re: wiki issues inregards to fetching plugins
On 2007-03-12 13:04:05 -0400, Guy Hulbert wrote: > On Mon, 2007-03-12 at 09:53 -0700, Ask Bjørn Hansen wrote: > > If there's some problem with the contrib section in our regular svn, > > The problem is that almost no-one has access (which you did explain to > me in response to my code.google tracker) so the wiki is being used as a > source code repository. I've have several times offered to act as a "human gateway" to the contrib directory. That is, I will add a subdirectory below contrib for anyone who asks and check in and update plugins people send to me. So far nobody has taken me up on that offer. (Yes, a repository where everybody could have write access to their own subtree would be better - but as long as there are only two people who have contributed anything (and at least one of them (me) has commit rights anyway) I can understand that the repository owners don't want to invest work into the svn infrastructure.) hp -- _ | Peter J. Holzer| I know I'd be respectful of a pirate |_|_) | Sysadmin WSR | with an emu on his shoulder. | | | [EMAIL PROTECTED] | __/ | http://www.hjp.at/ |-- Sam in "Freefall" signature.asc Description: Digital signature
Re: wiki issues inregards to fetching plugins
On Mon, 2007-03-12 at 10:14 -0700, Ask Bjørn Hansen wrote: > > The problem is that almost no-one has access [...] > > I believe we've given a contrib directory to everyone who asked so > far. :-) That's what you said before but I thought that you also mentioned some complication (possibly temporary) in adding accounts. > > >> we could move it to code.google.com. > > > > Does that solve the access problem? Does it include a suitable > source > > code repository component? > > It has svn. So is this the preferred path then ? Should we wait for you to set it up or just charge ahead ? -- --gh
Re: wiki issues inregards to fetching plugins
On Mar 12, 2007, at 10:04 AM, Guy Hulbert wrote: On Mon, 2007-03-12 at 09:53 -0700, Ask Bjørn Hansen wrote: Oh no, please don't use Sourceforge for anything. :-) What's wrong with Sourceforge (just curious) ? The interface is a pain to use -- in particular the "let's now click 8 times to download a file" thing. If there's some problem with the contrib section in our regular svn, The problem is that almost no-one has access [...] I believe we've given a contrib directory to everyone who asked so far. :-) we could move it to code.google.com. Does that solve the access problem? Does it include a suitable source code repository component? It has svn. - ask -- http://develooper.com/ - http://askask.com/
Re: wiki issues inregards to fetching plugins
On Mon, 2007-03-12 at 09:53 -0700, Ask Bjørn Hansen wrote: > Oh no, please don't use Sourceforge for anything. :-) What's wrong with Sourceforge (just curious) ? > > If there's some problem with the contrib section in our regular svn, The problem is that almost no-one has access (which you did explain to me in response to my code.google tracker) so the wiki is being used as a source code repository. > > we could move it to code.google.com. Does that solve the access problem? Does it include a suitable source code repository component? -- --gh
Re: wiki issues inregards to fetching plugins
On Mar 10, 2007, at 2:36 PM, James Turnbull wrote: It is a bit of a annoyance for getting something in the distfiles and I would like to avoid it. I have been thinking of just mirroring them on my site till the situation chances. This issue has been around for a while. There is the contrib section of the package that plug-ins can be added to. But how about a Sourceforge project for user-created qpsmtpd plug-ins? I'd be happy to set one up - and grant appropriate SVN access to all who wanted to contribute. Oh no, please don't use Sourceforge for anything. :-) If there's some problem with the contrib section in our regular svn, we could move it to code.google.com. For larger plugins I'd encourage distribution via CPAN and the new "plugin in a module" loading thing (Qpsmtpd::Plugin::Foo). - ask -- http://develooper.com/ - http://askask.com/
Re: wiki issues inregards to fetching plugins (and new versions, and duplicates)
On Mar 12, 2007, at 16:21, Nick Leverton wrote: On Saturday 10 March 2007 10:12, Johan Almqvist wrote: On Mar 9, 2007, at 21:15, Vulpes Velox wrote: I just noticed some on created a PAM plugin, but it is currently just a wiki page currently. I was just planning of trying it out after As the author of the current authcheckpassword, I just want to make sure I understand the issue here. You can just copy-paste the plugin into a file and add it to your port/distro? I did quite a bit of work based on your excellent plugin, Johan, and came up with a generic checkpassword plugin which copes with the two incompatible orders of checkpassword arguments used in the wild, and also supports all AUTH methods that qpsmtpd does. I'm using it with Dovecot IMAP's checkpassword. and I can submit authorised mail through qpsmtpd using my Dovecot credentials. Kewl :) I still have some changes which Ask suggested to apply to my auth/checkpassword, but I'd like to know what we should do about this sort of situation. I don't want to usurp Johan's checkpassword in the Wiki with my own, as his may fill someone's needs better than my fancier version does. I could create another page but then it gets confusing. How can we have a repo which holds alternative plugins for the same functionality, without confusing users ? What do you all think ? You could just make a new section further down on the page, maybe with its own header? -Johan
Re: wiki issues inregards to fetching plugins (and new versions, and duplicates)
On Saturday 10 March 2007 10:12, Johan Almqvist wrote: > On Mar 9, 2007, at 21:15, Vulpes Velox wrote: > > I just noticed some on created a PAM plugin, but it is currently just > > a wiki page currently. I was just planning of trying it out after > As the author of the current authcheckpassword, I just want to make > sure I understand the issue here. You can just copy-paste the plugin > into a file and add it to your port/distro? I did quite a bit of work based on your excellent plugin, Johan, and came up with a generic checkpassword plugin which copes with the two incompatible orders of checkpassword arguments used in the wild, and also supports all AUTH methods that qpsmtpd does. I'm using it with Dovecot IMAP's checkpassword. and I can submit authorised mail through qpsmtpd using my Dovecot credentials. Kewl :) I still have some changes which Ask suggested to apply to my auth/checkpassword, but I'd like to know what we should do about this sort of situation. I don't want to usurp Johan's checkpassword in the Wiki with my own, as his may fill someone's needs better than my fancier version does. I could create another page but then it gets confusing. How can we have a repo which holds alternative plugins for the same functionality, without confusing users ? What do you all think ? Nick
Re: wiki issues inregards to fetching plugins
On Sun, 2007-11-03 at 09:36 +1100, James Turnbull wrote: > But how about a Sourceforge project for user-created qpsmtpd plug-ins? > I'd be happy to set one up - and grant appropriate SVN access to all who > wanted to contribute. +1 -- --gh
Re: wiki issues inregards to fetching plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > It is a bit of a annoyance for getting something in the distfiles and > I would like to avoid it. I have been thinking of just mirroring them > on my site till the situation chances. This issue has been around for a while. There is the contrib section of the package that plug-ins can be added to. But how about a Sourceforge project for user-created qpsmtpd plug-ins? I'd be happy to set one up - and grant appropriate SVN access to all who wanted to contribute. I'd also be happy to migrate existing plug-ins from their disparate locations to Sourceforge. I think whatever happens there needs to be some central collection point for plug-ins - rather than the 7-8 locations (including the Wiki) that there are now. Regards James Turnbull - -- James Turnbull <[EMAIL PROTECTED]> - --- Author of Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) Hardening Linux (http://www.amazon.com/gp/product/159059/) - --- PGP Key (http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x0C42DF40) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF8zL89hTGvAxC30ARAuMLAKCFxkj7zv7eCmP26T0efhvoGLF1VQCg0han BPuF/Jt3Xj2i8syiCCRW5wo= =RiV+ -END PGP SIGNATURE-
Re: wiki issues inregards to fetching plugins
On Sat, 10 Mar 2007 11:12:01 +0100 Johan Almqvist <[EMAIL PROTECTED]> wrote: > > On Mar 9, 2007, at 21:15, Vulpes Velox wrote: > > > I just noticed some on created a PAM plugin, but it is currently > > just a wiki page currently. I was just planning of trying it out > > after copying it to a file, but the problem comes in is that if > > it works, I would like to write up a small port for installing it > > or include it in the qpsmtpd port for windows, but being a wiki > > page current it is not possible. Who would be the proper person > > or the like to poke some place in regards to getting it fixed? I > > also noticed the auth_imap and authcheckpassword are the same way. > > As the author of the current authcheckpassword, I just want to > make sure I understand the issue here. You can just copy-paste the > plugin into a file and add it to your port/distro? I am just going to copy and paste it now, for the PAM one, but if it works I would like to add it to the FreeBSD ports tree. yours also interested me as well. > Is the problem that you want to retrieve the plugin > programmatically (possibly at install-time)? The plugin would need > to be hosted somewhere. My server doesn't have the reliability for > such a thing, so maybe someone could add the plugin to svn or gcode > if that's the current repository (or give me access so I can do > it)... It is a bit of a annoyance for getting something in the distfiles and I would like to avoid it. I have been thinking of just mirroring them on my site till the situation chances.
Re: wiki issues inregards to fetching plugins
On Mar 9, 2007, at 21:15, Vulpes Velox wrote: I just noticed some on created a PAM plugin, but it is currently just a wiki page currently. I was just planning of trying it out after copying it to a file, but the problem comes in is that if it works, I would like to write up a small port for installing it or include it in the qpsmtpd port for windows, but being a wiki page current it is not possible. Who would be the proper person or the like to poke some place in regards to getting it fixed? I also noticed the auth_imap and authcheckpassword are the same way. As the author of the current authcheckpassword, I just want to make sure I understand the issue here. You can just copy-paste the plugin into a file and add it to your port/distro? Is the problem that you want to retrieve the plugin programmatically (possibly at install-time)? The plugin would need to be hosted somewhere. My server doesn't have the reliability for such a thing, so maybe someone could add the plugin to svn or gcode if that's the current repository (or give me access so I can do it)... -Johan
wiki issues inregards to fetching plugins
I just noticed some on created a PAM plugin, but it is currently just a wiki page currently. I was just planning of trying it out after copying it to a file, but the problem comes in is that if it works, I would like to write up a small port for installing it or include it in the qpsmtpd port for windows, but being a wiki page current it is not possible. Who would be the proper person or the like to poke some place in regards to getting it fixed? I also noticed the auth_imap and authcheckpassword are the same way.
