Thomas,

I open source world it is very common to have a package with binary and package with source files as well. You may find a lot of examples of this. BTW, 
Linux usually does not require root privileges to install a package.

Leonid.

Thomas Preisler wrote:
>
> >> Alexander's idea there should be a checkbox checked by default - "Add
> >> binary".
> Adding a checkbox raises some usability issues: What if you check the box, modify the entry, and then uncheck the box. Should it then remove what you 
have edited? It's probably better with a button but where should it be?
>
> About automatically adding project sources: I fail to see the value of adding buildable project source to a SVR4, RPM, Debian package. Who would do 
that? Creating a zip or tar file with the sources is perhaps useful, but the other packages are meant to be installed and who wants to install project sources 
(as root!) on a system? Isn't that the job of the source control system (cvs, mercurial, ...) to do exactly this? I may see the value of automatically Zip or tar 
up project sources but not for 'real' packages.
>
> --thomas
>
> Stepan Doubrava wrote:
>> It sounds like a good idea: "Adding groups of files (sources, binaries, etc) instead of having to select files one by one"
>>
>> I only have two remarks:
>> * In 2) you have mentioned a button that changes its name depending on the context, which is not recommended practice.
>> * Just to clarify, the current mechanism can theoretically be used for adding/removing any files, but typically it will be used for licenses, readmes etc. 
Right?
>>
>> regards
>> Stepan
>>
>> Leonid Lenyashin wrote:
>>> Oh! I think Alexander brought up a very interesting usability idea! I'd rephrase it in other way.
>>> 1) We already put a binary to the package by default. In the spirit of Alexander's idea there should be a checkbox checked by default - "Add binary".
>>> 2) There is a suggestion to simplify addition of source files (everything that is necessary to build the binary, but no libraries). For this we can add 
checkbox unchecked by default (or maybe a button) - "Add source files" (if it is a button if pressed it should change to "Remove source files").
>>> 3) Current mechanism used to add files to the package should be only used to add readme's, licenses, howto's and may be some binaries.
>>> What do people think? I like the idea!
>>>
>>> Stepan, what do you think?
>>>
>>> Leonid.
>>>
>>> Perepelica Alexander wrote:
>>>> Hi, Thomas!
>>>> I see feature to add some files. But I mean not that way. Project has file list which are needed for project build and I think this feature must (IMHO) 
have possibilities to add some external files to package (how you did realize) but for source file maybe should be a possibilities add or not add for source 
file and binary file. This behavior is how for binary rpm or src-rpm package which have or binary file with some config-files (external to project) and src-
rpm package which have only file which must have user to build binary