Hi,
Would it be possible to include the keywords in the .info file?
The point is that, at the moment I have to note down the keywords
somewhere and it becomes sometimes messy, when e.g. I write 2 or 3
SlackBuilds at the same time (my notes keeper gets messy;)).
The bigger point is that, it
On 09/06/2015 10:43 AM, Daniil Bratashov wrote:
I have to build and maintain a Gausssum software that require the
python3 versions of matplotlib, numpy and all of its dependencies. May
be it is worth to check if python3 is installed and build also python3
versions of libraries if so by default?
> Would it be possible to include the keywords in the .info file?
>
> The point is that, at the moment I have to note down the keywords
> somewhere and it becomes sometimes messy, when e.g. I write 2 or 3
> SlackBuilds at the same time (my notes keeper gets messy;)).
>
> The bigger point is
> while attempting to build libmspack, I got an error saying gzip: stdin: not
> in gzip format. Attempting to manually download, I went to the
> http://www.cabextract.org.uk/libmspack/ web site and was presented with a
> suspension page at http://www.cabextract.org.uk/cgi-sys/suspendedpage.cgi
Ok
while attempting to build libmspack, I got an error saying gzip: stdin: not
in gzip format. Attempting to manually download, I went to the
http://www.cabextract.org.uk/libmspack/ web site and was presented with a
suspension page at http://www.cabextract.org.uk/cgi-sys/suspendedpage.cgi
I did find
On 09/07/2015 02:03 PM, Marcel Saegebarth wrote:
On 09/06/2015 10:43 AM, Daniil Bratashov wrote:
I have to build and maintain a Gausssum software that require the
python3 versions of matplotlib, numpy and all of its dependencies. May
be it is worth to check if python3 is installed and build
On 09/06/2015 10:43 AM, Daniil Bratashov wrote:
> I have to build and maintain a Gausssum software that require the
> python3 versions of matplotlib, numpy and all of its dependencies. May
> be it is worth to check if python3 is installed and build also python3
> versions of libraries if so by
On 07/09/15 14:54, Willy Sudiarto Raharjo wrote:
Would it be possible to include the keywords in the .info file?
The point is that, at the moment I have to note down the keywords
somewhere and it becomes sometimes messy, when e.g. I write 2 or 3
SlackBuilds at the same time (my notes keeper
> Come to think of it -- the source for cabextract must also be
> unavailable, so I've uploaded that too. (It may take a few minutes
> for mirrors to synchronize.)
>
> http://sourceforge.net/projects/slackbuildsdirectlinks/files/cabextract/cabextract-1.4.tar.gz
> md5sum unchanged:
Come to think of it -- the source for cabextract must also be
unavailable, so I've uploaded that too. (It may take a few minutes
for mirrors to synchronize.)
http://sourceforge.net/projects/slackbuildsdirectlinks/files/cabextract/cabextract-1.4.tar.gz
md5sum unchanged:
On 07/09/15 23:27, Andrzej Telszewski wrote:
On 07/09/15 14:54, Willy Sudiarto Raharjo wrote:
Would it be possible to include the keywords in the .info file?
The point is that, at the moment I have to note down the keywords
somewhere and it becomes sometimes messy, when e.g. I write 2 or 3
The other thing to keep in mind is this: the database keeps track of the
keywords that have already been associated with the SlackBuild. The only
reason you would need to worry about that after the original submission is
if you come up with additional keywords, which shouldn't happen often
unless
On 07/09/15 23:55, B Watson wrote:
On 9/7/15, Christoph Willing wrote:
There is nothing preventing you from adding whatever you like to your
own local .info files - just remember to remove anything additional
before submitting to SBo.
Yep, but that requires
On 08/09/15 00:41, JK Wood wrote:
unless you're dealing with systemd-level feature creep.
Please keep the list free from political issues ;)
--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
> And I just wanted to keep my keywords in place...
> You're on higher level, methinks ;)
Lower level really -- it just doesn't fit in my head these days :-(
Cheers
-D.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
On 9/7/15, Christoph Willing wrote:
> There is nothing preventing you from adding whatever you like to your
> own local .info files - just remember to remove anything additional
> before submitting to SBo.
Or just include a file called keywords.txt in the tarball. I
On 08/09/15 00:34, David Spencer wrote:
I will keep the keywords in a separate file and just won't include it in the
upload.
How about using dokuwiki? It's how I keep all my maintaining info,
including version numbers, upstream URLs to check for new versions,
mailing list and bugtracker URLs,
> I will keep the keywords in a separate file and just won't include it in the
> upload.
How about using dokuwiki? It's how I keep all my maintaining info,
including version numbers, upstream URLs to check for new versions,
mailing list and bugtracker URLs, other distro's packaging repos for
18 matches
Mail list logo