Re: [Lazarus] Managing Packages with many versions

2017-03-31 Thread Mattias Gaertner via Lazarus 
On Fri, 31 Mar 2017 15:03:11 -0300
"Marcos Douglas B. Santos via Lazarus" 
wrote:

>[...]
> Yes, but as Michael said, I need to have many copies of the sources.
> I thought that I could use just one source and many /libs directories with
> the .ppu's
> 
> What do you think?

I guess different versions have different sources, don't they?

Mattias
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Online Package Manager

2017-03-31 Thread Alexey via Lazarus 

On 31.03.2017 21:43, Balázs Székely via Lazarus wrote:

- OPM becomes faster
- it's more easier to maintain
etc..



IMO benefit will be. it is "easier to maintain". Each developer which 
wants to send json,
makes GH acc, then clones OPM repo, then sends pull req. No emails. Zip 
can be send in GH post.


--
Regards,
Alexey

--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Online Package Manager

2017-03-31 Thread Balázs Székely via Lazarus 
@Alexey
Ok. Let's assume for a moment we move everything to GitHub. First I write to
every single developer and ask them to make a GitHub account. By some
miracle, everyone agrees and suddenly we are on GitHub. What would be the
benefits? Until now I did not have to deal with the external json files, it
was the package maintainer job to maintain those jsons. If we implement your
idea I have one more GitHub account to take care of, which is not a big deal
if there is a clear benefit like:
- OPM becomes faster
- it's more easier to maintain
etc..




--
View this message in context: 
http://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-Online-Package-Manager-tp4049766p4051310.html
Sent from the Free Pascal - Lazarus mailing list archive at Nabble.com.
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Online Package Manager

2017-03-31 Thread Alexey via Lazarus 
It must not be the problem. Many apps use GH, and they need patches on 
GH, and users make them on GH.




however some of the developers
prefer GitHub, others BitBucket or SourceForge. It's very hard to convince
somebody to move just for the sake of OPM.


--
Regards,
Alexey

--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Managing Packages with many versions

2017-03-31 Thread Marcos Douglas B. Santos via Lazarus 
On Fri, Mar 31, 2017 at 1:18 PM, Mattias Gaertner via Lazarus <
lazarus@lists.lazarus-ide.org> wrote:

> The IDE searches a lpk (correct name and version) and the
> corresponding .ppu files are stored relative to the lpk. See here
> http://wiki.freepascal.org/Lazarus_Packages#Different_
> versions_of_a_package
>

Mattias,

Yes, but as Michael said, I need to have many copies of the sources.
I thought that I could use just one source and many /libs directories with
the .ppu's

What do you think?

Best regards,
Marcos Douglas
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Online Package Manager

2017-03-31 Thread Werner Pamler via Lazarus 

Am 31.03.2017 um 14:06 schrieb Alexey via Lazarus:

 GetMem,
it would be very good, if all Json files, for components,
will be hosted on one Github repo. Now they are distributed
(on NNN servers, etc).
You can make repo for them.

Alexey


I don't see any advantage. Someone (GetMem?, you?) would have to get the 
developers access to that repository. The developers needs another 
password for a system which he does not need for anything else. Now the 
developer stores the update-json at a place where he already has access 
to. That's just perfect.


--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Online Package Manager

2017-03-31 Thread Balázs Székely via Lazarus 

> @DougC
> Seems to me you should have at minimum 3 status for packages:
> New - Not yet installed but available in repository
> Updated - Already installed but a new version is in repository
> Up-To-Date - Already installed and installed version is same as in
> repository
> Using "new" for both "not yet installed" and "installed but with available
> updates" is confusing.

Thank you for the suggestions. I agree, the whole system is somewhat
confusing, especially if you take into account that the packages can also be
updated from the maintainers webpage. I did my best to explain how it works:
http://wiki.freepascal.org/Online_Package_Manager#Difference_between_download.2Finstall.2Fupdate


> @Alexey
> it would be very good, if all Json files, for components,
> will be hosted on one Github repo. Now they are distributed
> (on NNN servers, etc).
> You can make repo for them.

We did try to move all the json to one place, however some of the developers
prefer GitHub, others BitBucket or SourceForge. It's very hard to convince
somebody to move just for the sake of OPM.



--
View this message in context: 
http://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-Online-Package-Manager-tp4049766p4051305.html
Sent from the Free Pascal - Lazarus mailing list archive at Nabble.com.
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Managing Packages with many versions

2017-03-31 Thread Michael Van Canneyt via Lazarus 



On Fri, 31 Mar 2017, Marcos Douglas B. Santos via Lazarus wrote:


On Fri, Mar 31, 2017 at 11:54 AM, Michael Van Canneyt via Lazarus <
lazarus@lists.lazarus-ide.org> wrote:


Put the various versions  in different directories. The IDE will use the
correct one based on the dependencies and the location. Every version
needs to have been opened once in the IDE.

I use it all the time. Works fine, except some rather exotic error messages
if the IDE doesn't find a matching version.



That is a way, thanks.
But I am thinking something like bellow:


Below. Bellow is something a cow does ;-)



smartfoo
 \lib
   \i386-win32\
 \1.0
 \1.1
 \1.2.3
 *.ppu (trunk)
   \x86_64-win64
 \1.0
 *.ppu (trunk)


My point is each project just use PPU files, not the real sources because I
would like
to have just one source.
The correct way is the author freeze the version using a label, but I can
do this myself locally. Then, I can compile and copy the PPU files for the
right lib\\.

But using this way I will need to set up which path to use when I add a
package into the project, right?
What do you think about it?


AFAIK The IDE will not work with that.

It needs the actual sources of each version. 
So you need multiple directories with the sources of each version.


FPC itself can work with this, if properly configured.


Michael.
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Managing Packages with many versions

2017-03-31 Thread Marcos Douglas B. Santos via Lazarus 
On Fri, Mar 31, 2017 at 12:22 PM, Michael Van Canneyt via Lazarus <
lazarus@lists.lazarus-ide.org> wrote:

> Below. Bellow is something a cow does ;-)
>

 Yeah, sorry.  :)



> AFAIK The IDE will not work with that.
>
> It needs the actual sources of each version. So you need multiple
> directories with the sources of each version.
>
> FPC itself can work with this, if properly configured.
>

Well, Ok. I will use as you explained. Thanks.
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

[Lazarus] Managing Packages with many versions

2017-03-31 Thread Marcos Douglas B. Santos via Lazarus 
Hi,

I would like to know how I can manager my 3rd packages with different
version.

For example, imagine that:
You have got a package called SmartFoo.lpk version 1.0.
You are using the master/trunk version.
Whe you compile it you got this: smartfoo\lib\x86_64-win64\*ppu, *.o, etc

Now you can use this package in your projects.

Then, the author update this package to 2.0 version.
Imagine that you have many projects using version 1.0 but you would like to
update to 2.0 to work in just one project.

The problem is: I don't want to work in other projects right now but you
need to mantain them compilable with the version 1.0 of SmartFoo if you
need it any time.

What is the best approach to deal with it?

I've already read the Wiki http://wiki.freepascal.org/Lazarus_Packages but
I can not realize how IDE will know about the right *.ppu files to use.


Best regards,
Marcos Douglas
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Online Package Manager

2017-03-31 Thread Alexey via Lazarus 

 GetMem,
it would be very good, if all Json files, for components,
will be hosted on one Github repo. Now they are distributed
(on NNN servers, etc).
You can make repo for them.

Alexey
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Linux 64 to Linux ARC crosscompile was:Lazarus and Windows 10 IoT

2017-03-31 Thread Andrea Mauri via Lazarus 


P.S.2
Interesting idea would be create utility which will build only
cross-compilers based on FPC already installed (like does FpcUpDeluxe
but without need/overhead of SVN checkout and Lazarus build
functionality). May be only ZIP archive with needed utilities + script
which will do needed tasks.


+1
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] Online Package Manager

2017-03-31 Thread DougC via Lazarus 
Seems to me you should have at minimum 3 status for packages:

New - Not yet installed but available in repository

Updated - Already installed but a new version is in repository

Up-To-Date - Already installed and installed version is same as in repository



Using "new" for both "not yet installed" and "installed but with available 
updates" is confusing.



 On Wed, 29 Mar 2017 07:37:37 -0400 Balázs Székely via Lazarus 
lazarus@lists.lazarus-ide.org wrote 




Online Package Manager shows the packages with "new" icon if the latest

 release time was in the given number of days, but shows them with normal

 icon if they are older than that days regardless if they are up-to-date

 or not.

 I my opinion:

 - It would be better to show up-to-date packages with normal icon

 and

 - Show all packages with "new" icon if their last release is newer than

 the installed one...




The idea was to notify the user if something has changed in the main 
repository. With your method non-installed packages wouldn't show up as "new" 
packages. For example if a completely new package is added to the main 
repository, you cannot see it as new, which is not optimal in my opinion.Beside 
if a new update is available a bold NEW text appears in the update column(see 
attachment).







-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] fpDebug error "Debug information not available"

2017-03-31 Thread Gabor Boros via Lazarus 

2017. 03. 28. 20:14 keltezéssel, Ondrej Pokorny via Lazarus írta:

Hello,

I want to test the fpDebug debugger. I followed
http://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-Need-testers-for-the-a-new-debugger-td4037911.html

When I run a LCL application, I get the following error within Lazarus IDE:

[Window Title]
project1 - Lazarus IDE v1.7
[Content]
No Dwarf-debug information available. The debugger will not function
properly. [CurrentProcess=TDbgWinProcess,DbgInfo=TFpDwarfInfo]
[OK]

I tried various "Type of debug info" in Project Options. The last I tried:

Do you have any hints?

OS: Win 10 64bit
Lazarus: trunk 1.7 32bit

Ondrej


Hi Ondrej and All,

For me Automatic and Stabs give the above error message and works with 
the other three options. Tried with Win10 64bit, FPC 3.0.2 32bit, 
Lazarus trunk 54502 (build with a simple "make" command then installed 
components\lazdebuggers\lazdebuggerfp\lazdebuggerfp.lpk).


Gabor
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus