>> We only support git. cgit is just web interface so can see other's work
>
> I upload my SlackBuilds to GitHub
> (https://github.com/drgibbon/slackbuilds), is there any way for that to
> be incorporated into the workflow? I find making a tar archive/uploading
> to the website to be quite unwield
On 03/06/2017 02:22 AM, Willy Sudiarto Raharjo wrote:
>> Do you prefer one method over another?
>
> We only support git. cgit is just web interface so can see other's work
I upload my SlackBuilds to GitHub
(https://github.com/drgibbon/slackbuilds), is there any way for that to
be incorporated int
On Sun, Mar 05, 2017 at 11:24:34PM +0700, Willy Sudiarto Raharjo wrote:
> > For the moment SBo prefers tarballs, well, for the moment that's the
> > only option.
> >
> > There is no git for ordinary users and maintainers as of now.
>
> That's not true
> we do allow "some" maintainers to have thei
> I am pretty sure that this, more cvs/svn orientated branching strategy is
> not optimal.
>
> There is no need for users to have branches, they should have forks.
> There they can branch, and create for these branches pull requests.
>
> Of course you can create also branches per user, but this o
> Here's i found a 404 error when trying downloading gecko-mediaplayer.
>
> So... please change download URL to "sboarch":
>
> http://slackware.uk/sbosrcarch/by-md5/d/1/d13303664fcbb7f3b1273be4b1aa1b1e/gecko-mediaplayer-1.0.8.tar.gz
>
>
> or to:
>
> https://storage.googleapis.com/google-code-a
>> You could take pull requests from every trust able person fore each package,
>> the maintainer models is total obsolete that only scales bad, distributes
>> work bad, and is a bottleneck by design.
>
> Who, or what, is going to do the required testing?
Well, I agree with David. I think the m
Here's i found a 404 error when trying downloading gecko-mediaplayer.
So... please change download URL to "sboarch":
http://slackware.uk/sbosrcarch/by-md5/d/1/d13303664fcbb7f3b1273be4b1aa1b1e/gecko-mediaplayer-1.0.8.tar.gz
or to:
https://storage.googleapis.com/google-code-archive-downloads/v2/
> There is no need for users to have branches, they should have forks.
> There they can branch, and create for these branches pull requests.
We do have the vague intention of using Gitlab like that, but it is an
ongoing research project, because first we need an answer to the
question below:
> Yo
I am pretty sure that this, more cvs/svn orientated branching strategy is
not optimal.
There is no need for users to have branches, they should have forks.
There they can branch, and create for these branches pull requests.
Of course you can create also branches per user, but this only pollutes t
> For the moment SBo prefers tarballs, well, for the moment that's the
> only option.
>
> There is no git for ordinary users and maintainers as of now.
That's not true
we do allow "some" maintainers to have their own branches in our GIT
repository. See https://slackbuilds.org/cgit/slackbuilds/
> Do you prefer one method over another?
We only support git. cgit is just web interface so can see other's work
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@sla
On 05/03/17 15:38, Jeremy Hansen wrote:
On Sun, Mar 5, 2017, 3:10 AM Willy Sudiarto Raharjo
mailto:will...@slackbuilds.org>> wrote:
> I've always wondered about this. Wouldn't it be easier for the
> maintenance team to deal with _some_ form of version control, rather
> than updated
On Sun, Mar 5, 2017, 3:10 AM Willy Sudiarto Raharjo
wrote:
> > I've always wondered about this. Wouldn't it be easier for the
> > maintenance team to deal with _some_ form of version control, rather
> > than updated archives delivered through slackbuilds.org?
>
> We do have and we used git
>
> se
> I've always wondered about this. Wouldn't it be easier for the
> maintenance team to deal with _some_ form of version control, rather
> than updated archives delivered through slackbuilds.org?
We do have and we used git
see the web-based interface here:
https://slackbuilds.org/cgit/slackbuilds
14 matches
Mail list logo
