Robby,
There will always been suggestions to change/improve things in some
way. You can always just say NO like you did this time around :).
Although I agree it could be useful in rare circumstances, I can never
see myself making any use of such addition in the near future.
On Mon, May 12, 2008
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
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
I think it would benefit users, but I don't think it would help the admins at
all. Couldn't a line be added at the *end* of every .info file with minimal
effort? Y'all could just set up a loop to cat the line into the file and
re-tar the slackBuilds.
Anyhoo, it's no big deal to me; I just th
Phillip Warner wrote:
I think there should be something in the slackBuilds that says what
slackware version the script was designed for. I suggest specifying the
slackware version in the .info file and the .slackBuild file.
This can be useful for two purposes. One, it can help you to use the
Iskar Enev wrote:
JK Wood wrote:
That's why I use these magic things called "folders" to keep track of
such things.
Imagine that for *some* reason you don't have the initial information -
how would you organize the folders then?
I also think it's a good idea to include the slackware version
JK Wood wrote:
That's why I use these magic things called "folders" to keep track of
such things.
Imagine that for *some* reason you don't have the initial information -
how would you organize the folders then?
I also think it's a good idea to include the slackware version in the
.info file
;
> Message: 4
> Date: Sun, 4 May 2008 14:11:17 -0500
> From: alkos333
> Subject: Re: [Slackbuilds-users] specifying slackware version in the
> slackBuilds
> To: "SlackBuilds.org Users List"
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
> Having a
version
information would be helpful in these cases.
--phil
Message: 4
Date: Sun, 4 May 2008 14:11:17 -0500
From: alkos333
Subject: Re: [Slackbuilds-users] specifying slackware version in the
slackBuilds
To: "SlackBuilds.org Users List"
Message-ID:
Content-Type: text/plain; cha
Having a version number associated with a script would be helpful if
you didn't have access to SBo repo, or a mirror.
On Sun, May 4, 2008 at 2:08 PM, Andrew Brouwers <[EMAIL PROTECTED]> wrote:
> Hi Phil,
>
> What's the purpose, then, of segregating the repo's on
> slackbuilds.org? That's the r
Hi Phil,
What's the purpose, then, of segregating the repo's on
slackbuilds.org? That's the reason why there are separate paths for
different slackware versions (and why not all scripts are available in
each of them).
Andrew
On Sun, May 4, 2008 at 2:40 PM, Phillip Warner <[EMAIL PROTECTED]> wro
I think there should be something in the slackBuilds that says what slackware
version the script was designed for. I suggest specifying the slackware
version in the .info file and the .slackBuild file.
This can be useful for two purposes. One, it can help you to use the right
script for a cer
14 matches
Mail list logo
