pkw wrote:
I didn't make the original request, but I piped in and offered to
do the work, so for my part I'm just making it clear I'm not trying
to make anyone's life harder. I was completely satisfied with the
1st response that it wouldn't get done. I only offered to do the
work because Rob k
On Mon, May 12, 2008 at 03:36:39PM -0400, [EMAIL PROTECTED] wrote:
> On Monday 12 May 2008 15:08:01 Robby Workman wrote:
> > If you have a package lying around and it's not clear what version
> > it was compiled for, then you need a better system of organization.
> >
>
> Now we are getting down t
Mon May 12 20:27:20 UTC 2008
development/kdesvn: Updated for version 0.14.3. Thanks to Michiel. --rworkman
libraries/libopensync: Reverted to version 0.22 because some things that
depend on it can't use the newer releases yet. Thanks to Michael Wagner
for pointing out the incompatibilities and
On Monday 12 May 2008 15:08:01 Robby Workman wrote:
> If you have a package lying around and it's not clear what version
> it was compiled for, then you need a better system of organization.
>
Now we are getting down to the crux of the problem, no matter what we
did someone would say you should h
pkw wrote:
I'm potentially prepared to do the work, but I need to clarify one
point. It is only important to me if the meta-info of the target
slackware version lives *with* the package. [1]
It would need to be in the package name itself or in the .SlackBuild.[0]
Well, if that's a require
On Sun, May 11, 2008 at 11:10:44PM -0500, Robby Workman wrote:
> Quite frankly, I don't see how this addition would help *us* (that
> is, the admins). While it's not a huge effort to implement once the
> initial addition is done, the initial change of adding the relevant
> line to *.info files to
