queue-developers

[Queue-developers] Releasing development snapshot as 1.40.1

[W. G. K. <wer...@ya...>]

Hi all,

It's time for a new release to make our developments available to a
wider audience.

I'm planning to release the current development snapshot as 1.40.1.

QingLong is doing a lot of concurrent development.

I will have to do some as well (mainly legal stuff adding copyright
notices to QingLong's work to protect GNU Queue's open source status.
Anything addition more than about four lines or so of code needs a
copyright comment.)

I'm planning to release a snapshot of the development version as GNU
Queue 1.40.1 (a development release) over the next 24 hours (probably
sooner rather than later) so please be aware of this. If you have any
objections to this (the current snapshot doesn't work well, for example)
let me know.

We will need to establish a more concrete policy on this in the future.

Re: [Queue-developers] Releasing development snapshot as 1.40.1

[Santeri <sa...@xp...>]

W. G. Krebs wrote:

> Hi all,
> 
> It's time for a new release to make our developments available to a
> wider audience.
> 
> I'm planning to release the current development snapshot as 1.40.1.
> 
> QingLong is doing a lot of concurrent development.
> 
> I will have to do some as well (mainly legal stuff adding copyright
> notices to QingLong's work to protect GNU Queue's open source status.
> Anything addition more than about four lines or so of code needs a
> copyright comment.)
> 
> I'm planning to release a snapshot of the development version as GNU
> Queue 1.40.1 (a development release) over the next 24 hours (probably
> sooner rather than later) so please be aware of this. If you have any
> objections to this (the current snapshot doesn't work well, for example)
> let me know.
> 
> We will need to establish a more concrete policy on this in the future.

I've been trying to get the latest cvs version working under freebsd4.2 
today.  The new utmp/wtmp stuff from rxvt is a complete mess, the
configure.in doesn't work properly and so on.  for example
it didn't even care if there was no wtmp.h.

Additionally there were quite a few missing system headers like
sys/time.h, netinet/in.h...

And finally when I got it to compile it didn't work. but that was 
propably my own fault, something with the hostname I think. :(

Anyway, I'll try to clean up the fixes tomorrow and post a diff somewhere.

/santtu

Re: [Queue-developers] Releasing development snapshot as 1.40.1

[W. G. K. <wer...@ya...>]

OK, we'll hold off on taking the snapshot.

I'd like to do it within a week or so, though, so that we can get our lat=
est
developments into the hands of more users.

(Another thing we could try is a slightly older CVS snapshot. If anyone h=
as
preferences, let me know.)

Santeri Hernej=E4rvi wrote:

> W. G. Krebs wrote:
>
> > Hi all,
> >
> > It's time for a new release to make our developments available to a
> > wider audience.
> >
> > I'm planning to release the current development snapshot as 1.40.1.
> >
> > QingLong is doing a lot of concurrent development.
> >
> > I will have to do some as well (mainly legal stuff adding copyright
> > notices to QingLong's work to protect GNU Queue's open source status.
> > Anything addition more than about four lines or so of code needs a
> > copyright comment.)
> >
> > I'm planning to release a snapshot of the development version as GNU
> > Queue 1.40.1 (a development release) over the next 24 hours (probably
> > sooner rather than later) so please be aware of this. If you have any
> > objections to this (the current snapshot doesn't work well, for examp=
le)
> > let me know.
> >
> > We will need to establish a more concrete policy on this in the futur=
e.
>
> I've been trying to get the latest cvs version working under freebsd4.2
> today.  The new utmp/wtmp stuff from rxvt is a complete mess, the
> configure.in doesn't work properly and so on.  for example
> it didn't even care if there was no wtmp.h.
>
> Additionally there were quite a few missing system headers like
> sys/time.h, netinet/in.h...
>
> And finally when I got it to compile it didn't work. but that was
> propably my own fault, something with the hostname I think. :(
>
> Anyway, I'll try to clean up the fixes tomorrow and post a diff somewhe=
re.
>
> /santtu
>
> _______________________________________________
> Queue-developers mailing list Que...@li...
> To unsubscribe, subscribe, or set options:
> http://lists.sourceforge.net/lists/listinfo/queue-developers

Re: Re: [Queue-developers] Releasing development snapshot as 1.40.1

[QingLong <qin...@Bo...>]

	Hello!

On Thu, Mar 15, 2001 at 04:33:52PM -0500, W. G. Krebs wrote:
>
> I'd like to do it within a week or so, though, so that we can get our latest
> developments into the hands of more users.
>
> (Another thing we could try is a slightly older CVS snapshot. If anyone has
> preferences, let me know.)
>
   I would like to have a chance to try to adapt new code to freebsd
 before releaseing it. Hope Santeri Hernej?rvi will work with me on it.

      QingLong.

Re: Re: [Queue-developers] Releasing development snapshot as 1.40.1

[QingLong <qin...@Bo...>]

On Thu, Mar 15, 2001 at 08:35:53PM +0100, Santeri Hernej?rvi wrote:
>
> I've been trying to get the latest cvs version working under freebsd4.2 
> today.  The new utmp/wtmp stuff from rxvt is a complete mess,
>
   Hmmm.
 I've asked you to test that stuff against freebsd quite a while ago,
 we would have enough time to correct it.
 Well, we are where we are, so please try to install rxvt on your system
 to check if pristine rxft wtmp-stuff works for you.
 There are chances that I haven't imported that code well enough.

>
> Additionally there were quite a few missing system headers like
> sys/time.h, netinet/in.h...
>
   Would you be so kind as to try to wrap those #include's in proper
 `#ifdef HAVE_xxx'? Does it help?

>
> And finally when I got it to compile it didn't work.
> but that was propably my own fault, something with the hostname I think. :(
>
   A bit more details please: did it sefault? debug output? etc...

>
> Anyway, I'll try to clean up the fixes tomorrow and post a diff somewhere.
>
   As that were probably my changes that screwed the code on freebsd,
 please send a copy of the diffs to me. Thank you.

      QingLong.