Hey,
> Yes, that's precisely what I had in mind. As for the location, it
> would make sense if others would cast their vote. One option would be
> macports-base (as that's what we are basically shipping), else
> macports-infrastructure.
>
> Till the time it is decided where we should push the
OK sorry, actually if we are just pushing Dockerfile with it's setup
documentation then I guess, there's no need of another repo.
So it could be something like
- Dockerfile and it's documentation
- Azure CI to test run if the dockerfile works perfectly
- Moving forward as you said we can add
Hey,
Ok great. I will write a basic guide by tonight.
Just tell me where should I push the code.
I would prefer if it is a different repository atleast for now but I am
fine with anything.
Thanks,
Karan Sheth
On Mon, Jul 15, 2019 at 2:58 AM Mojca Miklavec wrote:
> Dear Karan,
>
> On Wed, 26
Hey,
My suggestion would be: could you perhaps share the sources
> (Dockerfile I guess; together with some basic usage instructions)? We
> could probably add a repository under github/macports-gsoc or so. Then
> I could at least build an image locally instead of getting something
> incompatible.
Dear all,
As you may know, I am working on "Automating Packaging for MacPorts” using
upt (https://framagit.org/upt/upt) as my GSoC project. So I just wanted to
inform the MacPorts community about the current status of the project and
there are a few topics where we would like some input:
Project
Hey,
I really want to thank you guys for selecting me.
I am really overjoyed and excited about working with you guys!:):)
I will make sure to always put in my best efforts and to do the job
I'm assigned to the best of my abilities. I look forward to an awesome
summer, coding and getting to know
Hey,
So I came across this recent mail in mailing list[1] stating the PR
for deletion of PHP PEAR ports.
I went through a few of the ports and it seems that once the update
functionality of UPT is completed the updation of these ports could be
easily automated just by adding a PEAR frontend to
Hey,
Just a gentle reminder, If I could get a reply to my previous mail as
the deadline for submission is now less than a day and I would like to
submit the proposal well before the deadline.
Sorry for remailing.
Thanks,
Karan Sheth
On Mon, Apr 8, 2019 at 12:05 AM KARAN SHETH wrote:
>
> Hey,
>
Hey,
> There's nothing specific that I would want to comment on.
> Well, to me it's not entirely clear how the automatic updates would be
> supposed to work, but ...
I made some changes to the update part, is it better now or am I still
missing something?
> And the stretch goals are somewhat
Hey,
> Check your dependencies; this should only happen if your port does not
> depend on the port that provides this file, i.e. python37. You might be
> overwriting the dependency by setting depends_lib rather than appending
> to it.
Changing from this :
if {${name} ne ${subport}} {
Hey,
On Fri, Apr 5, 2019 at 11:59 AM Mojca Miklavec wrote:
>
> Dear Karan,
>
> No time to test now, but what does "port contents py37-upt" say? It
> could be called upt-py37 or something. That's a weird consequence of
> supporting multiple version of python at the same time.
Port py37-upt
Hey,
So I tried porting upt and in the process had to port spdx-lookup and spdx.
These are the portfiles for the same [1],[2],[3].
When I try to install upt there is no error message but while trying
to run upt via a terminal directly it says the command not found
whereas if I go to python
Hey,
On Wed, Apr 3, 2019 at 2:35 AM Mojca Miklavec wrote:
>
> Dear Karan,
>
> you may put such statistics and suggestions for action plans in the proposal
> (or appendix to proposal).
Ok, I'll do that soon
> What about pypackage -> py-pypackage? (I miss such entries on the list,
> unless
Hey,
Just to see how many ports will we have to rename if we take on this
path I ran a quick script and following were the results:
PyPI NameMacports NameNumber
package package 10
package py-package 769
package
Hey,
On Mon, Apr 1, 2019 at 8:34 PM Mojca Miklavec wrote:
> On Mon, 1 Apr 2019 at 16:38, Renee Otten wrote:
> >
> > there is a figure showing a WebUI that is not described (personally I am
> not sure if that would be needed anyway).
>
> My assumption was that Karan planned to submit "an
Hey,
On Mon, Apr 1, 2019 at 8:08 PM Renee Otten wrote:
> hi Karan, Mojca, Cyril,
>
>
> I am happy to help with testing and provide feedback. I quickly glanced
> over the proposal draft and agree with what Cyril said; in addition, there
> is a figure showing a WebUI that is not described
Hey,
On Mon, Apr 1, 2019 at 3:09 PM Mojca Miklavec wrote:
> Dear Karan,
>
> Just a few quick notes (for others as well).
>
> On Sun, 31 Mar 2019 at 22:00, KARAN SHETH via macports-dev wrote:
> >
> > I have uploaded the project.
> > Macports-Backend : https:/
Hey,
I have completed most of the changes that you suggested.
Haskell frontend has been now added to technical details and I guess I got
why you were saying that why it would be tricky to add it as a frontend.
Web UI has been removed seeing that it won't be a good add-on as suggested
by Renne.
Hey,
I will do the suggested changes and also add the pending stuff and then
submit the draft proposal by tomorrow.
Thanks for the review.
Thanks,
Karan Sheth
On Mon, Apr 1, 2019 at 1:16 AM Cyril Roelandt
wrote:
> Hello,
>
> On 2019-04-01 00:30, KARAN SHETH wrote:
> > I have started drafting
Hey,
I have uploaded the project.
Macports-Backend : https://github.com/Korusuke/upt-macports
NPM-Frontend : https://github.com/Korusuke/upt-npm
Note: Macports backend is forked from original repo by Mojca.
Thanks,
Karan Sheth
On Sun, Mar 31, 2019 at 10:56 PM Renee Otten wrote:
> hi Karan,
Hey,
I have started drafting my proposal for GSoC 2019. It would be great to
have a review on it before I submit the same.
It's still a WIP, once done I will submit the same to GSoC draft proposal.
Link:
Hey,
Sorry but I haven't uploaded the git repo yet as there is no Readme, I will
do it soon and ping you once it done.
Thanks,
Karan Sheth
On Sun, Mar 31, 2019 at 10:56 PM Renee Otten wrote:
> hi Karan,
>
>
> where is your repository for this project? I wanted to take a look and
> possibly
Hey Cyril,
I have made a merge request as you suggested, please review it if anything
is wrong.
Thanks,
Karan Sheth
On Sat, Mar 30, 2019 at 4:16 AM Cyril Roelandt
wrote:
> On 2019-03-30 03:35, KARAN SHETH wrote:
> > I had to update a bit of upt-cpan as it was not parsing description
>
Hey,
On Mar 29 2019, at 3:26 am, Mojca Miklavec wrote:
>
> > master_sites git+https://github.com/request/request.git
>
> This line looks a bit suspicious. If the files live on github, we might want
> to use the github PortGroup anyway, but let's leave that detail for later ...
yeah the link
Hey,
On Thu, Mar 28, 2019 at 8:48 PM Mojca Miklavec mailto:mo...@macports.org)> wrote:
>
> We are looking forward. I hope that Cyril will also help with the process (my
> encounter with UPM so far was for the full two hours while hacking on it :).
I've written a basic npm frontend and macports
Resending the mail cause, previous mail was not sent to mailing list.
On Wed, Mar 27, 2019 at 2:10 PM Mojca Miklavec wrote:
> Dear Karan,
>
> I'm just answering a small part of your question here, a bit more about
> upt while CC-ing its author & potential mentor:
>
> On Tue, 26 Mar 2019 at
an,
>>
>> Warmly welcome to the MacPorts community!
>>
>> On Mon, 25 Mar 2019 at 20:36, KARAN SHETH via macports-dev wrote:
>>
>>> Hey there,
>>> I would like to start by saying this is not GSoC Proposal as the
>>> subject says but I had no idea
Hey Mojca,
Thanks for replying.
On Tue, Mar 26, 2019 at 3:00 AM Mojca Miklavec wrote:
> Dear Karan,
>
> Warmly welcome to the MacPorts community!
>
> On Mon, 25 Mar 2019 at 20:36, KARAN SHETH via macports-dev wrote:
>
>> Hey there,
>> I would like to st
Hey there,
I would like to start by saying this is not GSoC Proposal as the
subject says but I had no idea what else to call it. This is just to make
contact with you regarding a GSoC Project idea that I would really like to
do.
My name is Karan Sheth. I have attached a doc link wherein
29 matches
Mail list logo
