Is SLKBUILD usage compulsory?

[rsamurti]

Hi,

Is using SLKBUILD compulsory?

Anand

[gapan]

Hi Anand!

No it isn't. If you want to use Slackbuilds/buildscripts, you are free to do so.

[releasedinjapan]

Hi,

So it means that we can use SlackBuilds for packages submitted for inclusion in Salix? Do SlackBuilds need to be named build-<package_name>.sh? I tested slkbuild and that makes it dead easy to create build scripts, but I'd like to be able to maintain packages on slackbuilds.org as well.

It opens another question: can you / will you use existing SlackBuilds to add new packages to Salix repository?

[gapan]

Of course you can use Slackbuilds and, no there is no rule for build-$name.sh naming. You can use $name.Slackbuild naming as with all slackware packages.

[thenktor]

But I'd appreciate it to have the SlackBuild included in the package in /usr/src/$packagename-$version

[rsamurti]

Yes. I feel using SLKBUILD makes package creation process more systematic.

Anand

[ajaykumar.mysore]

Yes. I feel using SLKBUILD makes package creation process more systematic.

Anand

But Sir we don have a complete control over the programming package which we are dealing with right..

[JRD]

No you have the whole control of it. Study SLKBUILD please.

[bruenig]

bruenig here, what is this I see?

[gapan]

Hi bruenig