> sorry to bother again i want to make a submission of wlroots again but it
> say *File exists;* a submission by the name 'wlroots' is already pending
> approval. it was already deleted before.
Done, you can resubmit
again, please read my note in last public update
Please note that if you want
sorry to bother again i want to make a submission of wlroots again but it
say *File exists;* a submission by the name 'wlroots' is already pending
approval. it was already deleted before.
best regards!
___
SlackBuilds-users mailing list
i submit again libseat as seats, but i have the same problem as before with
wlroots
it say File exists a submission by the name 'libseat' is already pending
approval.
i want to submit wlroots and sway again. Thanks a lot and sorry to bother.
___
Hi,
I can't re-upload my SB for wireplumber, it says : "File exists; a
submission by the name 'wireplumber' is already pending approval."
And when I try to remove it: "The file wireplumber.tar.gz does not exist
in pending"
Can you at this ?
Regards
> The buildscript has
>
> # For python 3.x support.
> if [ "${PYTHON3:-yes}" == "yes" ]; then
> CFLAGS="$SLKCFLAGS" \
> python3 setup.py build
> python3 setup.py install --root=$PKG
> fi
>
> while the README stats
>
> Note: To install python 3 bindings set PYTHON3=yes.
> # PYTHON3=yes
> Setting 'make -j$NUMJOBS' seems a safer path, and is what Pat does in
> Slackware source.
Because in most of the time, people use his binary packages, not
building from source (only some people do this, like nobodino who helped
him testing that slackware always build from source).
In case of
The buildscript has
# For python 3.x support.
if [ "${PYTHON3:-yes}" == "yes" ]; then
CFLAGS="$SLKCFLAGS" \
python3 setup.py build
python3 setup.py install --root=$PKG
fi
while the README stats
Note: To install python 3 bindings set PYTHON3=yes.
# PYTHON3=yes ./miniupnpc.SlackBuild
On 4/3/22 11:59, B. Watson wrote:
> How about you do this instead?
>
> if [ -z "$MAKEFLAGS" ]; then
>NUMJOBS="${NUMJOBS:-1}"
>export MAKEFLAGS="-j$NUMJOBS"
> fi
> make
>
> ...that way, your builds work the way you want: they respect NUMJOBS
> if MAKEFLAGS isn't set... but they'll still
On 4/3/22 12:34, Dave Woodfall wrote:
> On 03/04/22 22:19,
> Ozan Türkyılmaz put forth the proposition:
>> Pzt, 2022-04-04 tarihinde 01:22 +0700 saatinde, Willy Sudiarto Raharjo
>> yazdı:
>>>
>>>
>>> You can just export MAKEFLAGS in your machine to achive same results
>>> Don't expect others to
On 03/04/22 22:19,
Ozan Türkyılmaz put forth the proposition:
> Pzt, 2022-04-04 tarihinde 01:22 +0700 saatinde, Willy Sudiarto Raharjo
> yazdı:
> >
> >
> > You can just export MAKEFLAGS in your machine to achive same results
> > Don't expect others to use same machine as yours and we often test
>
Il giorno dom 3 apr 2022 alle ore 20:59 Slackbuilds
ha scritto:
> Most of my testing for submission is in a VM (either 2, 4 or 6 cores,
> depending on how many I fire up on the Ryzen 9). Settings MAKEFLAGS
> will hide NUMJOBS and is not appropriate since it obscures what was
> used. My VMs may
Pzt, 2022-04-04 tarihinde 01:22 +0700 saatinde, Willy Sudiarto Raharjo
yazdı:
>
>
> You can just export MAKEFLAGS in your machine to achive same results
> Don't expect others to use same machine as yours and we often test
> those
> scripts in a VM with only small specs.
>
Don't do that.
> I see no logical reason not to use -j${NUMJOBS} for those sources that
> support it, and set -j1 as the default. This is a decision that can be
> left to the buildscript maintainer to determine from testing. It does
> not need to be, IMHO, an arbitrary global rule.
It may not be a problem for
On 4/3/2022 1:22 PM, Willy Sudiarto Raharjo wrote:
For compatibility, the default will be one core/thread. Please do not
remove. This is a feature and not a bug.
You can just export MAKEFLAGS in your machine to achive same results
Don't expect others to use same machine as yours and we often
On 4/3/22 11:22, Willy Sudiarto Raharjo wrote:
>> For compatibility, the default will be one core/thread. Please do not
>> remove. This is a feature and not a bug.
>
> You can just export MAKEFLAGS in your machine to achive same results
> Don't expect others to use same machine as yours and we
On Sun, 3 Apr 2022, Slackbuilds wrote:
Therefore, I will be adding back in to all the buildscripts under my
care, for those that can support it:
NUMJOBS=${NUMJOBS:-1}
make -j${NUMJOBS}
There's no need for this. You can just 'export MAKEFLAGS=-j8' or
whatever in your environment. A lot of
> For compatibility, the default will be one core/thread. Please do not
> remove. This is a feature and not a bug.
You can just export MAKEFLAGS in your machine to achive same results
Don't expect others to use same machine as yours and we often test those
scripts in a VM with only small specs.
Hello Admins,
I get it. We want to ensure compatibility over a wide variety of
computer hardware and build systems. However, IMHO this far into the
21st Century, we need to realize that most SBo users are on x86_64
architecture and will have multicore processors on any laptop or desktop
CPU. My
Hi,
thank you for the heads up!
In addition, I am always happy to hear about people being involved in science.
:-)
All the best to you, and of course to our beloved Slackware (and the **one**
and the **others** behind it. :-))
--
Best regards,
Andrzej Telszewski
19 matches
Mail list logo
