I was really hoping I would not have to have my SlackBuild be named with the capital letter this time but w/e ;p moreover I think its confusing.
> Message: 6 > Date: Wed, 7 Feb 2018 09:05:32 +0700 > From: Willy Sudiarto Raharjo <will...@slackbuilds.org> > To: slackbuilds-users@slackbuilds.org > Subject: Re: [Slackbuilds-users] basilisk.SlackBuild > Message-ID: <16163ada-ba76-fdc4-38e5-400876366...@slackbuilds.org> > Content-Type: text/plain; charset="windows-1252" > > > I was wondering if basilisk.SlackBuild could be renamed to > > basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source > > for some time now. I just have not submitted it to SBo but I plan to > > very shortly and think it would be better this way. > > there's no need to rename the SlackBuild, just add a note in the README > that it uses binary repackaging instead of compiling from source. > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 195 bytes > Desc: OpenPGP digital signature > URL: > <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180207/d6cb642d/attachment-0001.asc> > > ------------------------------ > > Message: 7 > Date: Tue, 06 Feb 2018 22:32:58 -0500 > From: "Ed Ender" <skae...@excite.com> > To: "SlackBuilds.org Users List"<slackbuilds-users@slackbuilds.org> > Subject: Re: [Slackbuilds-users] basilisk.SlackBuild > Message-ID: <20180206223258.15...@web005.roc2.bluetie.com> > Content-Type: text/plain; charset=UTF-8 > > Or you can do like what was done with the Pale Moon SlackBuilds, the > repackage one is smallcase, and the compile one is capitalized. > > -----Original Message----- > From: "Willy Sudiarto Raharjo" [will...@slackbuilds.org] > Date: 02/06/2018 08:08 PM > To: slackbuilds-users@slackbuilds.org > Subject: Re: [Slackbuilds-users] basilisk.SlackBuild > > > I was wondering if basilisk.SlackBuild could be renamed to > > basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source > > for some time now. I just have not submitted it to SBo but I plan to > > very shortly and think it would be better this way. > > there's no need to rename the SlackBuild, just add a note in the README > that it uses binary repackaging instead of compiling from source. > > > -- > Willy Sudiarto Raharjo > > > > > > ------------------------------ > > -----Original Message----- > > From: "Willy Sudiarto Raharjo" [will...@slackbuilds.org] > > Date: 02/06/2018 08:08 PM > > To: slackbuilds-users@slackbuilds.org > > Subject: Re: [Slackbuilds-users] basilisk.SlackBuild > > > >> I was wondering if basilisk.SlackBuild could be renamed to > >> basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source > >> for some time now. I just have not submitted it to SBo but I plan to > >> very shortly and think it would be better this way. > > > > there's no need to rename the SlackBuild, just add a note in the README > > that it uses binary repackaging instead of compiling from source. > > > >
signature.asc
Description: PGP signature
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
