[Slackbuilds-users] couple questions

Adnan Hodzic absinthesyringe at gmail.com
Wed Aug 1 14:35:00 UTC 2007


> > 1. What would be the best way to handle the software which source code
> > is available trough CVS only?
>
> I think we have something like this in the repo but I forget what, hopefully
> someone else can field this question.

I wanted to this with Wormux, do the latest svn, but we talked about
it and concluded that it wouldn't fit the whole "Slackware style"
because mostly latest svn/cvs stuff is new and exiting ... it is also
unstable.

So IMO I'd say stay away from CVS/SVN and stick to latest stable editions.

On 8/1/07, Erik Hanson <erik at slackbuilds.org> wrote:
> On Aug 01, 2007, at  2:15 PM, Aleksandar B. Samardzic wrote:
>
> > Got some questions regarding creating build scripts:
> >
> > 1. What would be the best way to handle the software which source code
> > is available trough CVS only?
>
> I think we have something like this in the repo but I forget what, hopefully
> someone else can field this question.
>
> > 2. What would be the best way to report changes needed for build
> > scripts (and links from SB.o site) when new package version appears
> > (for example, current SQLite version is 3.4.1, containing some rather
> > important updates, while build script, and link from SB.o site, point
> > to version 3.3.14) - to ask for change on this list, to send patch, or
> > something else?
>
> Sending a patch to this list, or submitting an updated script. If you're
> not able to work with the scripts then just emailing the list (especially
> concerning security updates) is fine.
>
> > 3. Is there an example of build script for a CMake based package in
> > one of existing SB.o build scripts?
>
> A quick grep shows that we have cmake in the 11.0 repo here:
> http://slackbuilds.org/repository/11.0/development/cmake/
> I can't comment on why it doesn't exist for 12.0, which is unfortunate
> because cdrkit for 12.0, located here:
> http://slackbuilds.org/repository/12.0/system/cdrkit/
> appears to use it, but it's not listed as a dependency.
>
> > 4. There are lots of build scripts here:
> > http://www.slackware.com/~alien/slackbuilds/, some of which are not
> > available here at SB.o, so - are there any plans to integrate these
> > (for example, I would be very interested in Boost build script
> > available from SB.o, but I see no point in creating another script,
> > when one is available at
> > http://www.slackware.com/~alien/slackbuilds/boost/)?
>
> That is the repo of one of our admins. There can be any reason, but
> usually it is a more complex script that doesn't fit the guidelines of
> SBo. This isn't uncommon, really. We need to keep the scripts at SBo
> pretty strict (read: simple) so that any admin can maintain them if
> necessary.
>
> You should have full confidence using alien's slackbuilds, along with
> other team members that choose to keep their own repositories.
>
> Erik Hanson
> --
> http://slackbuilds.org/
>
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>
>



More information about the Slackbuilds-users mailing list