Caveat: this rant doesn't bring much added value to David's answer to
the OP. Still, here it is, as maybe not every submitter is aware of how
the information about deps is used by some tools.
Le 10/03/2018 à 20:23, B Watson a écrit :
> On 3/10/18, David Spencer wrote:
>
>> slack-required in the
On 3/10/18, David Spencer wrote:
> slack-required in the SBo repository is pointless, we already have
> REQUIRES= in the .info file. When your preferred build tool builds the
> package, it can create and package the slack-required file, and/or
> create a .dep file, and/or PACKAGE REQUIRED line in
On 03/10/2018 10:50 AM, Andrew wrote:
> I think we should have MAKEDEP and RUNDEP lines in info file for listing
> build-time and runtime dependencies there.
No need to complicate things, we're only concerned with what's required
to build a package. Anything that can be removed later should alre
On 03/10/2018 09:50 AM, Andrew wrote:
> Also, can we add SHA256SUM to .info file for slackers with paranoia? ;-)
>
> --
> Andrew
+1
I wouldn't call it paranoia, just peace of mind.
--
Brenton Earl
___
SlackBuilds-users mailing list
SlackB
On March 10, 2018 3:37:56 PM UTC, David Spencer
wrote:
>
>*Personal opinions*
>
>slack-conflicts is a rare case. At the moment we add some advice in
>README and we add %README% to REQUIRES=. I would be personally quite
>happy to kill %README% forever, by putting a new CONFLICTS= line in
>the .i
> Are we allowed to add slack-required, slack-suggests and slack-conflicts
> files to our scripts?
At the moment, no. If you can find some, it was probably a mistake, or
maybe a specially negotiated exception, but I don't think there are
any :)
*Personal opinions*
slack-required in the SBo repos
