[Slackbuilds-users] specifying slackware version in the slackBuilds

[JK Wood]

That's why I use these magic things called "folders" to keep track of such
things.

On Mon, May 5, 2008 at 10:17 AM, Phillip Warner <pc_warner at yahoo.com> wrote:

> Even if you do have access to the repo it would be quicker to simply check
> the .info or .slackBuild file to see what slackware version it is for
> instead of comparing it to what is in the repo.  Either that, or people
> would just download a fresh copy just to be sure (sometimes the program
> version is the same in different repos), but that could waste bandwith.
>
> The whole point is that if you have a folder full of slackBuilds, what
> version are they for?  Say you have a package you want to install that was
> built with a slackBuild.  What version was it built for?  Having the
> slackware 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; charset=UTF-8
>
> 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 wrote:
> > 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 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
> right
> > > script for a certain slackware version (some differ in more than just
> subtle
> > > ways). Second, it is also possible that having the version stated can
> > > help you determine what slackware version the package was built for.
> This
> > > is possible if the slackware version is mentioned in the .slackBuild
> file,
> > > as it is included as a part of every SBo package. So, to determine
> what
> > > version of slackware the SBo package is intended for, you can just
> look at
> > > that file in the package.
> > >
> > > --phil
> > >
> > >
> > > ________________________________
> > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
> it
> > > now.
> > >
> > >
> > > _______________________________________________
> > > Slackbuilds-users mailing list
> > > Slackbuilds-users at slackbuilds.org
> > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > >
> > > Please read the FAQ - http://slackbuilds.org/faq/
> > >
> > >
> > _______________________________________________
> > Slackbuilds-users mailing list
> > Slackbuilds-users at slackbuilds.org
> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >
> > Please read the FAQ - http://slackbuilds.org/faq/
> >
>
>
> ------------------------------
>
>
>
> ------------------------------
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it
> now.<http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ>
>
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
> Please read the FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080505/dc81a698/attachment.htm>