On 14-Oct-98 Duncan Haldane wrote:
>
>On 14-Oct-98 Karl O. Pinc wrote:
>> People seem to be using the diald-config-0.1 package a lot, probably because
>> it was released as an i386 rpm before rpm supported "noarch" as an
>> architecture. It is very old. The latest version is at least 1.2.1.
>
>
>Hmmm. I guess I did not carefully inspect the diald-0.16.5-201.src.rpm that
I
> patched up to diald-0.16.5a-1.src.rpm by restoring the dctrl patch
> to make dctrl work.
>
> It does mention you (Karl Pinc), and does produce a diald-config rpms
as
> well as a diald rpm. I suppose it is a "merge" of your (Karl)'s
work
> on configuration with Eric Schenk's stuff.
> From this point of view, I guess the diald rpm
> ought to be "pure eric" and diald-config should be "pure Karl".
Ohboy. I guess this means I have to take a look to be sure it's not a patched
up 0.1 release. It could be, because soon after I started releasing the
sample configurations as separate rpms, so people wouldn't have to worry about
new software clobbering their configuration.
>
>
> "diald-0.16.5-201" was been the only diald rpm for RedHat 5.x available
> for many months. The way RedHat contrib site works is that only the
> "newest" rpm as determined by version (here 0.16.5) and release (here
201)
> survives, the older ones get archived in /dev/null :( .
> Since 0.16.5a > 0.16.5, 0.16.5a rpms will supersede all 0.16.5 ones.
>
> Its certainly not good if the diald-config-0.16.5a-1 stuff is in fact
> obsoleted by more recent releases of Karl's config work as a seperate
> "noarch" rpm. (a problem with "noarch is that people looking for
> diald and diald-config rpms will not find them in the same directory)
I also put them on ftp://sunsite.unc.edu. They go with LDP documents to
determine what releases they keep, so it should be there.
>
>
> Karl, maybe you could sort out a new release (say diald-0.16.5a-2)that
> updates your scripts. I think the 0.16-5a numbering scheme is
consistent,
> as it implies that the patch level is essentially 5, but IS different.
> Maybe diald and diald-config should have seperate source rpms?
I guess I'll have to sort things out. After I get rid of the scsi problems on
my new computer. So who knows when.
I'm not opposed to a single source rpm. It seems Erik's about done with diald,
and diald-config's been stable and working (excepting some parts of clone
devices) for a long time. So maybe everything can be wrapped up together for
whoever wants to do more work. (I do have a 1.3.0 diald-config release, fixes
the 'clone' bugs, a little bit more doc, and an expermental feature. All the
newly documented configuration chocies don't work due to bug(s) in diald 16.4,
and I don't want to bother upgrading on my old machine. I need to test it with
the latest and greatest diald.
The one thing that diald-config does need is to have the README turned into a
man page. I worry that nobody can find the directions. Is this a problem?
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
