Re: [Slackbuilds-users] Keywords in info file

2015-09-08 Thread Miguel De Anda 
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 you're dealing with systemd-level feature creep.

--JK

Well that's good to know. I always open existing SlackBuilds as I submit an
update and copy paste all the fields. It would be nice to just have the
form read in values from tgz upload though.

M
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread Willy Sudiarto Raharjo 
> 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 will generally take me 1 or 2 days to
> submit the SlackBuild after it has been written and during these few
> days I come with new keywords that I have to note somewhere, and this
> somewhere does not help with the workflow. Having the keywords in the
> SlackBuild directory itself would improve the situation.
> 
> Maybe I'm a bit paranoid, but in general I'll try to add as many
> relevant keywords as possible, so that others that are thinking
> differently, have better chances of finding the SlackBuild.


Any real benefit of adding this keyword in the info file?

Currently, we store the keywords in the database so that it could be
used for searching purpose and easily modified without having to submit
a new package just to change the keywords.

Also, i personally disagree to use info file to store all the keywords,
since it would mean more checking during approval since a single mistake
in the .info files could cause some problem during public update.


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread Andrzej Telszewski 

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 gets messy;)).

The bigger point is that, it will generally take me 1 or 2 days to
submit the SlackBuild after it has been written and during these few
days I come with new keywords that I have to note somewhere, and this
somewhere does not help with the workflow. Having the keywords in the
SlackBuild directory itself would improve the situation.

Maybe I'm a bit paranoid, but in general I'll try to add as many
relevant keywords as possible, so that others that are thinking
differently, have better chances of finding the SlackBuild.



Any real benefit of adding this keyword in the info file?


As I explained before, it would save me from noting the keywords for new 
SlackBuilds on the back of the envelope...





Currently, we store the keywords in the database so that it could be
used for searching purpose and easily modified without having to submit
a new package just to change the keywords.

Also, i personally disagree to use info file to store all the keywords,
since it would mean more checking during approval since a single mistake
in the .info files could cause some problem during public update.


I'm not going to insist, as I have already workaround for the issue;)
From my point of view, including keywords would help me keep a little 
bit smaller mess on my notes.
But if you say it might make approval more cumbersome, then I said 
nothing. My few SlackBuilds per year is not much comparing to what you 
have to check during the approval.







___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/




--
Pozdrawiam,
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread Christoph Willing 

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
SlackBuilds at the same time (my notes keeper gets messy;)).

The bigger point is that, it will generally take me 1 or 2 days to
submit the SlackBuild after it has been written and during these few
days I come with new keywords that I have to note somewhere, and this
somewhere does not help with the workflow. Having the keywords in the
SlackBuild directory itself would improve the situation.

Maybe I'm a bit paranoid, but in general I'll try to add as many
relevant keywords as possible, so that others that are thinking
differently, have better chances of finding the SlackBuild.



Any real benefit of adding this keyword in the info file?


As I explained before, it would save me from noting the keywords for new
SlackBuilds on the back of the envelope...



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.


chris


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread JK Wood 
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 you're dealing with systemd-level feature creep.

--JK

On Mon, Sep 7, 2015 at 5:34 PM, David Spencer <
baildon.resea...@googlemail.com> 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, other distro's packaging repos for
> stealing patches ;-) lists of packages that depend on my packages ...
> and keywords.
>
> There's an SBo package for dokuwiki, and Giorgio the maintainer
> updated it just a couple of days ago :-)
>
> -D.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread Andrzej Telszewski 

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 additional work before submitting and probably 
often I would submit the .info with my own fields;)




Or just include a file called keywords.txt in the tarball. I don't think
it would cause any problems for the approval process (someone correct
me if I'm wrong). You'd just have to remember to paste its contents into
the submission form, when it comes time to submit the build.-- 


I don't think it's a good idea. This way people would start to include 
whatever they liked and it would become a mess for SBo crew.


I will keep the keywords in a separate file and just won't include it in 
the upload.


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread Andrzej Telszewski 

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
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread David Spencer 
> 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
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread B Watson 
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 don't think
it would cause any problems for the approval process (someone correct
me if I'm wrong). You'd just have to remember to paste its contents into
the submission form, when it comes time to submit the build.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread Andrzej Telszewski 

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, other distro's packaging repos for
stealing patches ;-) lists of packages that depend on my packages ...
and keywords.

There's an SBo package for dokuwiki, and Giorgio the maintainer
updated it just a couple of days ago :-)



And I just wanted to keep my keywords in place...
You're on higher level, methinks ;)

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keywords in info file

2015-09-07 Thread David Spencer 
> 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
stealing patches ;-) lists of packages that depend on my packages ...
and keywords.

There's an SBo package for dokuwiki, and Giorgio the maintainer
updated it just a couple of days ago :-)

-D.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/